Record RFC-0004's acceptance - #14
Merged
Merged
Conversation
The maintainer accepted the IPC design on 2026-08-01, in the form the 2026-07-30 prior-art review revised it to: synchronous unbuffered rendezvous, endpoints as RFC-0003 capability objects, virtual-register fast path with a bounded copying slow path, move-only capability transfer in messages, call with single-use first-class reply objects, and bounded notifications. Acceptance does not pre-empt the SS9 open questions, which join their named RFCs: copy-vs-map goes to the MMU RFC, multi-core rendezvous to the scheduler RFC, the register budget to the syscall ABI RFC. Both halves of the core mechanism are now accepted on paper, and RFC-0003 is already built and host-proven; the next design work is the initial kernel object set and bootstrap (RFC-0003 SS14.4), after which endpoints become the capability table's first real consumer. Logged in docs/CHANGELOG.md, as status changes always are. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
What
Records the maintainer's 2026-08-01 verdict: RFC-0004 (IPC) is accepted, in the form the 2026-07-30 prior-art review revised it to.
callwith single-use reply objects, bounded notifications — and that the §9 open questions remain expressly open, joining their named RFCs (copy-vs-map → MMU; multi-core rendezvous → scheduler; register budget → syscall ABI).docs/CHANGELOG.md, as status changes always are.What this unblocks
Both halves of the core mechanism are now accepted on paper, and RFC-0003 is already built and host-proven. The next design work is the initial kernel object set and bootstrap (RFC-0003 §14.4) — after which endpoints become the capability table's first real consumer.
Markdown and British-spelling gates clean.
🤖 Generated with Claude Code