RFC Index

Status: 32 RFCs: 11 accepted, 4 drafts with an accepted amendment, and 17 drafts.

Every change to the design of AnvayaOS goes through an RFC here: the problem, the decision, its security and audit impact, compatibility, and the evidence that would prove it. Each RFC states honestly how mature its claims are.

RFC Lifecycle

stateDiagram-v2
    direction LR
    [*] --> Draft
    Draft --> Accepted: reviewed and accepted
    Draft --> Rejected
    Accepted --> Superseded: replaced by a later RFC
    Draft --> Draft: amendment accepted (A1, A2, ...)

Maturity Labels

Label	Meaning
Stable	Accepted contract; implementers can rely on it
Evidence-backed prototype	Backed by working code and QEMU evidence, still being extended
Provisional	Parts accepted (for example an amendment), closure still pending
Planned	Proposed direction, not yet implemented
Rejected	Considered and declined
Superseded	Replaced by a later RFC

Index

RFC	Title	Status	Maturity
0001	Capability Model	Accepted	Stable
0002	Agent Execution Context Specification	Accepted	Stable
0003	RISC-V QEMU First-Light Boot Path	Accepted	Stable
0004	Local Capability and Blocking IPC Baseline	Accepted	Stable
0005	Bounded Object/Task Capability Table Slice	Accepted	Evidence-backed prototype
0006	Nucleus Contract	Accepted	Stable
0007	CSpace And Handle Representation	Accepted	Stable
0008	Memory Model	Draft	Evidence-backed prototype
0009	IPC Surface v2	Draft	Planned
0010	Syscall ABI	Accepted	Stable
0011	Scheduler Semantics	Draft	Planned
0012	Boot Contract v2	Draft	Planned
0013	DTB And FDT Scope	Draft	Planned
0014	RISC-V And CHERI Profile	Draft	Planned
0015	HAL And Board Profile	Draft	Planned
0016	Verification And CI Evidence Gates	Draft, A1 accepted	Provisional
0017	Userspace Process And ABI	Draft	Planned
0018	Init, Service Manager, And Registry	Draft	Planned
0019	Device Manager And Driver Model	Accepted	Stable
0020	Storage And Namespace	Accepted	Stable
0021	WASM Runtime And ANVAYA WASI	Draft	Planned
0022	Package/App Manifest And SDK Surface	Draft	Planned
0023	Agent Identity, Goals, World Model, And Approval	Draft, A1 accepted	Provisional
0024	Intelligence Broker	Draft, A1 accepted	Provisional
0025	Threat Model	Draft	Planned
0026	Constitutional Constraints And Hardware Escape	Draft	Planned
0027	Audit Immutability And Provenance	Draft	Planned
0028	PQC And Crypto Architecture	Draft, A1 accepted	Planned
0029	Security Response And Governance	Draft	Planned
0030	Device Mesh And Distributed Capabilities	Draft	Planned
0031	Energy Broker	Draft	Planned
0032	Capability Sockets And Network Service	Accepted	Stable

Each RFC's own Maturity Label section gives the exact scope and the evidence behind it.

Canonical Ledgers

VISION_TRACEABILITY.md maps manifesto and architecture claims to labels, RFCs and evidence.
ANVAYA_1_0_ACCEPTANCE.md maps the 1.0 production target to RFCs, required evidence and non-goals.

Adding an RFC

Copy template.md to the next numbered file.
Fill in motivation, decision, design, security impact, constitutional and audit impact, compatibility, validation and traceability.
Link every dependency explicitly, and state what is stable and what is provisional.
Open a pull request. An RFC is marked Accepted only once the project process has accepted it.

Local Checks

./scripts/check-rfc-ledger.sh

The check confirms that RFCs 0001 to 0031 exist and are not placeholders, that this index mentions every one of them, that each has maturity, security and traceability metadata, that dependency targets exist and form no cycle, and that both ledgers are present.

Repository	What it holds
anvaya	The operating system: nucleus, services, runtime and proofs
anvaya-site	Source of anvaya.dev
anvaya-docs	Documentation hub (planned)
anvaya-sdk	Developer SDK (planned)
anvaya-apps	Reference apps and demos (planned)
anvaya-hardware	Hardware specs and RISC-V extensions (planned)
anvaya-infra	CI/CD and infrastructure automation (planned)
.github	Organization profile and community files

Contributing

Please read CONTRIBUTING.md and follow the Code of Conduct. Design changes go through the RFC process. Report security issues privately, as described in SECURITY.md. Changes are recorded in CHANGELOG.md.

License

Licensed under either of the Apache License, Version 2.0 or the MIT License, at your option. See COPYRIGHT, NOTICE and third-party/.

Citation

@misc{anvayaos,
  title        = {AnvayaOS: The Operating System for the Intelligence Age},
  author       = {Alphin Tom},
  year         = {2026},
  howpublished = {\url{https://anvaya.dev}},
  note         = {Contact: info@anvaya.dev; GitHub: https://github.com/AnvayaOS}
}

Current release coordination

This repository follows the v1.8.2 patch line on the v1.8.1 maintenance release; exact source, scope and acceptance requirements are recorded separately from its component maturity. v1.9 development is deferred. Physical-board acceptance and external audit remain pending.