Skip to content

RFC: authenticated compute groups and worker ABI - #42

Draft
joshuajbouw wants to merge 2 commits into
mainfrom
codex/compute-abi-rfc-20261022
Draft

joshuajbouw wants to merge 2 commits into
mainfrom
codex/compute-abi-rfc-20261022

Conversation

@joshuajbouw

@joshuajbouw joshuajbouw commented Oct 22, 2026 •

Copy link
Copy Markdown
Member

Specify the draft compute-group authority and raw worker ABI before Linux Realm can depend on it. The proposal separates installer support preflight, authenticated package publication, and exact live UID/capsule/generation checks at activation and open; it maps distinct admission errors and retains worker/resource custody until native settlement.

The first public ABI-1 candidate supports bounded memory32 and memory64, the corrected advisory header, four optional worker imports supplied by the host, ordered BLAKE3-bound assets, finite job and startup fuel, stack-slot exports, and forced cancellation of atomic waits. Main and v2026.10.1 have no compute host, so the earlier experiment is not a shipped compatibility promise. Hosted OS trust and potential seL4 proofs remain separate from controller, engine, guest, and installed-package evidence.

Validation: RFC follows the repository's 0000 draft convention; git diff --check passes; related WIT #28 parses with no declaration-shape change. Keep this draft unmerged while finite startup fuel, registry publication fencing, the named unsupported-compute-host installer preflight, and real packaged Linux Realm boot are implemented and tested.

Signed-off-by: Joshua J. Bouw <jjb@unicity-labs.com>
Signed-off-by: Joshua J. Bouw <jjb@unicity-labs.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant