docs: amend roadmap + ADR 0003 for the swervebot monorepo - #37
Merged
Conversation
Reflects the xmAppSwerveBase -> xmAppSwerveBot two-tier restructure (xmAppSwerveBot#5, merged): - one application repo holds both tiers (base/, autonomy/) + the shared protocol/ library; the planned separate xmAppSwerveAutonomy sibling is retired. - Phase 0.5's swerve-base CAN client relocates from xmDriver to autonomy/can_client/ — the protocol is app-owned, so its client is app-specific, not a reusable family device (charters/gates). - Phase 0 protocol-spec + base-skeleton items marked done (merged software; teleop parity remains the hardware exit gate). - ADR 0003 xmApp rule: multi-tier apps are directories in one repo, not separate repos — the tier is a build target, not a product.
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.
Reflects the merged xmAppSwerveBot#5 (xmAppSwerveBase → xmAppSwerveBot, two-tier restructure):
xmAppSwerveBotholdingbase/+autonomy/+ the sharedprotocol/library; the planned separatexmAppSwerveAutonomysibling is retired.autonomy/can_client/— the protocol is app-owned, so its client is app-specific (charters/gates), and it links the sameprotocol/the base's server does.xmApprule gains the multi-tier clause: deployment tiers are directories in one repo, not separate repos — the tier is a build target, not a product.Docs-only.