An agent runtime's constitution, in markdown

What it does This repository collects the formal design proposals that govern Astrid’s boundary between kernel and user-space. The RFCs cover substantial changes to the host ABI, IPC protocol, capability model, manifest schema, VFS semantics, capsule interfaces, and SDK public API. Once merged, a proposal becomes the authoritative specification; implementations must conform to the text, not the reverse.

The interesting bit The project treats markdown files as the single source of truth for a runtime’s contract surface. Each RFC advances through a strict lifecycle—Draft, Active, Final, Withdrawn, Superseded—and maps directly to a feature flag in astrid-sdk, so new types surface in the SDK incrementally as proposals stabilize.

Key highlights

• Governs the full kernel-to-user contract: syscalls, IPC schemas, capability tokens, Capsule.toml manifests, and cross-capsule interfaces.
• Immutability by design: once an RFC reaches Final, breaking changes require a brand new proposal.
• SDK integration links each RFC to an astrid-sdk feature flag (rfc-1, all-rfcs, etc.), surfacing new types as proposals stabilize.
• The process is still bootstrapping: the only Active RFC is 0001, which defines the RFC process itself.

Caveats

• The specification library is almost entirely blank; beyond the meta-process document, no concrete contracts have been merged yet.
• Copyright dates of 2025–2026 suggest the runtime and its governance are both extremely young.

Verdict Worth bookmarking if you track agent runtime design or care about kernel-to-user-space contracts. Skip it if you need finished specifications to implement today.