What is this?
This repository holds RFCs (design proposals) that define any substantial change to the contract between Astrid's kernel and user-space, covering the host ABI, IPC protocol, capability model, manifest schema, VFS semantics, capsule interface standards, and the SDK's public API.
This repository holds RFCs (design proposals) that define any substantial change to the contract between Astrid's kernel and user-space, covering the host ABI, IPC protocol, capability model, manifest schema, VFS semantics, capsule interface standards, and the SDK's public API.Is this an actual software library, or just a set of design documents?It's purely a set of markdown specification documents and a governance process, not runnable code — the README states that implementations must conform to the RFCs, not the other way around.
It's purely a set of markdown specification documents and a governance process, not runnable code — the README states that implementations must conform to the RFCs, not the other way around.How do I propose a change via an RFC?Fork the repo, copy '0000-template.md' to 'text/0000-my-feature.md', fill in the motivation and reference-level spec, and open a pull request using that filename for discussion.
Fork the repo, copy '0000-template.md' to 'text/0000-my-feature.md', fill in the motivation and reference-level spec, and open a pull request using that filename for discussion.What kind of changes actually require writing an RFC?Anything touching the syscall table in astrid-sys, IPC topic/payload schemas, capability token format, the Capsule.toml manifest schema, VFS path resolution, new capsule interface standards, or breaking changes to the astrid-sdk public API.
Anything touching the syscall table in astrid-sys, IPC topic/payload schemas, capability token format, the Capsule.toml manifest schema, VFS path resolution, new capsule interface standards, or breaking changes to the astrid-sdk public API.Does merging an RFC mean the feature is ready to use?No — a merged RFC is only 'Active'; its types still need to be implemented behind feature flags in astrid-sdk and in reference capsules before it becomes 'Final' and stable.
No — a merged RFC is only 'Active'; its types still need to be implemented behind feature flags in astrid-sdk and in reference capsules before it becomes 'Final' and stable.How many RFCs exist right now?Just one — RFC 0001, 'RFC Process', currently marked as Active.
Just one — RFC 0001, 'RFC Process', currently marked as Active.What do the RFC lifecycle stages mean?Draft means the PR is open for discussion, Active means it's merged and being implemented in astrid-sdk, Final means it's implemented and stable, Withdrawn means it was closed without merging, and Superseded means a newer RFC replaced it.
Draft means the PR is open for discussion, Active means it's merged and being implemented in astrid-sdk, Final means it's implemented and stable, Withdrawn means it was closed without merging, and Superseded means a newer RFC replaced it.What is a 'capsule' in Astrid?Based on the referenced schemas, a capsule appears to be Astrid's unit of user-space code, described by a Capsule.toml manifest and conforming to defined capsule interface standards like tool schemas and cross-capsule contracts.
Based on the referenced schemas, a capsule appears to be Astrid's unit of user-space code, described by a Capsule.toml manifest and conforming to defined capsule interface standards like tool schemas and cross-capsule contracts.How does an accepted RFC actually reach the SDK?Once consensus is reached and the RFC is merged, a maintainer assigns it a sequential number, and implementation then proceeds in astrid-sdk behind feature flags plus in reference capsules.
Once consensus is reached and the RFC is merged, a maintainer assigns it a sequential number, and implementation then proceeds in astrid-sdk behind feature flags plus in reference capsules.What are similar projects?book, EIPs, spec, design, bips, spec, api-guidelines, swift-evolution
book, EIPs, spec, design, bips, spec, api-guidelines, swift-evolutionWhich topics is it in?spec-driven-development, governance, standards, access-control, specification, protocol, runtime, operating-system, kernel, template, architecture, sandbox
spec-driven-development, governance, standards, access-control, specification, protocol, runtime, operating-system, kernel, template, architecture, sandbox