Repository navigation
docs: define CrewBoss platform roadmap - #3
Merged
Merged
Conversation
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
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
Why
CrewBoss needs a concrete path from its current local Bash workflow to a reliable Firstmate competitor without copying Firstmate's branding or protocols. The original specification branch was based on main before PR #2, so its event baseline was stale. Review also exposed an overclaim in same-user process isolation and several smaller contract gaps.
Important decisions
crewboss emit,events.jsonl, and at-least-once delivery are treated as shipped baseline behaviorcrewboss.cli.v1JSON contract is implemented only in Go; Bash remains a frozen rollback engineunsafe-hostis explicitly advisorymodernc.org/sqliteImpact
This PR changes documentation only. It does not change current CrewBoss runtime behavior. The specification becomes the master contract for later per-release implementation plans.
Validation
bash tests/run: 100 tests passed, exit 0git diff --check: clean