docs(spec): record Phodopus successor direction in plugin runtime RFCs (CTX-0043) - #80
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.
Priority: P1 | Area: docs | Labels: docs, P1, area:docs, area:lua | Milestone: v0.1.0 | RFC: OQ-009 / OQ-014 | Task: CTX-0043
What
Records the Phodopus successor runtime direction in the plugin-ecosystem runtime RFCs, per bitty-docs ADR 0012 (accepted 2026-09-20). Adds direction only; promotes no status and rewrites no accepted evidence.
Phodopus (
https://github.com/bitty-terminal/phodopus) is the accepted successor Lua runtime.bitty-luastill depends onpiccolo = "0.3.3"; the migration is scheduled, not landed. The acceptedmlua/Lua 5.4 baseline and every dated measurement remain intact.Changed files
runtime/lua-runtime-rfc.md— ADR-0004 / technology-strategy clause now readspiccolowas the watch-list candidate, with the plugin-VM successor direction recorded as Phodopus (ADR-0012). Successor paragraph updated to keep the accepted baseline and currentpiccolopin explicit.runtime/isolation-resource-rfc.md— one clearly-marked successor-direction note; OQ-009 out-of-scope clause names ADR-0012; the RC table status paragraph gains a successor-direction sentence; the RC-1 row policy cell notes the successor enforcement engine while keeping thepiccoloFuel/wall evidence atd67a65b.runtime/plugin-host-runtime-rfc.md— successor-direction note; ADR-0005 out-of-scope clause names ADR-0012; the A.5Sendbullet records that Phodopus preserves the single-owner-thread boundary.Evidence preserved (not rewritten)
Nothing touched in the dated measurement evidence:
d67a65b(2026-08-27), CTX-0037 PR #68, CTX-0040, CTX-0049, CTX-0050, the RC-1..RC-11 ceilings, the P0 Review Sign-off rows, and the historical measurement blockquotes remain byte-for-byte as accepted.Honest-status caveat
piccolo 0.3.3remains the accuratebitty-luapin until an implementing task lands.Phodopus Plugin Runtime (Candidate)page staysdraft; this PR does not promote it.Gate evidence (this worktree)
Review ask
piccolopin is still accurate, and no dated measurement evidence or ADR history was rewritten.