[codex] Add repository runtime replacement plan#202
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
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.
Summary
.planning/repository_runtimeimplementation plan for replacingjido_agent_oswith a product-owned repository runtime.Jido.Podconversion, product entrypoint cutover, persistence/recovery, AgentOS removal, and final hardening.bw/ beadwork startup requirements fromAGENTS.mdwhile preserving the branch and PR workflow guidance.Why
bwis not available in this environment, and the runtime replacement work needs a concrete phased plan before code changes start. The plan keeps one runtime container per repository while usingJido.Podas the bounded pod topology primitive instead of copying AgentOS.Validation
git diff --check HEAD~1..HEADAGENTS.mdhas no remainingbw/ beadwork references withrg.No Mix tests were run because this PR only changes Markdown planning and repository instructions.