Skip to content

The Operating System for the Intelligence Age

New Foundations for Machines That Reason, Decide, and Act

ANVAYA is a clean-slate operating system built in the open on RISC-V. It is evidence-first: every release ships with a repeatable QEMU boot log, and nothing is claimed that a boot log cannot show.

FOR DEVELOPERS: a Rust nucleus on RISC-V where nothing has ambient authority — every syscall needs an explicit, revocable capability, every package ships a post-quantum signature checked against NIST's official test vectors, and every release must reproduce its own boot log under QEMU.

CURRENT RELEASE: V1.8.3 "INTERRUPT-DELIVERY REPAIR" v1.8.3 fixes the intermittent qemu-virt boot hang present since before v1.8.2: a device interrupt taken while a client or service runs in user mode is now claimed through the bare kernel map, fatal reports print through it, and a restarted driver binding drains the PLIC source its predecessor left latched. v1.8.2 added the shakti-cclass kernel target for a SHAKTI C-class bitstream (Buildable, QEMU shakti_c only), with OpenSBI and Rust machine-mode monitor lanes and a private loading kit for IIT Madras. Fresh exact-source local gates at the v1.8.3 tag cover all 135 model harnesses, pinned Verus obligations and negative controls, Lean, QEMU with both SHAKTI lanes, six-boot recovery and four crash cuts, ACVP, accounting and documentation. transport=service-loopback, polling=0 and kernel_fallbacks=0 remain; M1, M6 and M8 stay PARTIAL. v1.9 is deferred with its source and evidence preserved. QEMU-proven research software; physical board acceptance and external audit remain pending.

Read the ManifestoImplementation StatusLive Boot DemoMain Repository
v1.8.3 · PatchNIST ACVP PQC KAT-verifiedFormally Verified (bounded)Unsafe source measured
qemu-system-riscv64 · check-qemu-boot.sh

$ ANVAYA SCHEDULER PROCESS RUNTIME HELPER OK pid=0xa313 dispatches=37 returns=37 yields=0 exits=0 abi=0x1

$ ANVAYA LIVE TCP SOCKET OK service=0xa9d0 endpoint=203.0.113.10:443 state=established denials=1

$ ANVAYA NETWORK SERVICE CORE OK dns_records=1 dns_query=33 dns_response=49 dns_udp_query=61 dns_udp_response=77 dns_eth_query=75

$ ANVAYA SYSCALL TRAP RETURN OK task=0xa001 cause=0 resolution=0 denials=5

$ ANVAYA PROCESS DISPATCH REGISTRY OK pid=0xa31b satp=0x8a1010000008075b hits=2 denials=3 registered=2 cleared=2

$ ANVAYA PROCESS DISPATCH SRET CONTINUE OK pid=0xa31b satp=0x8a1010000008075b ecalls=3 continues=2 hits=3

$ ANVAYA VIRTIO DRIVER PERSISTENCE OK sector=4096 first=seeded second=verified service=userspace-driver client=block-adapter aec=1

$ ANVAYA WASM SERVICE LOADER IPC CONTINUITY AGGREGATE OK clients=4 services=4 storage=storage-roundtrip network=network-echo installer=hello-status registry=endpoint-receive

$ ANVAYA LIVE STORAGE CRATE OK service=0xa9d0 content_id_prefix=0x7a2a63f2beeef5fa bytes=16 roundtrip=1 denials=1

$ ANVAYA LIVE NETWORK SERVICE OK service=0xa9d0 name=live.anvaya.dev address=203.0.113.10 ttl=60 denials=1

$ ANVAYA LIVE SIGNED SERVICE OK service=0xa9d0 entry=0x40001000 code_paddr=0x80759000 package_bytes=3405 signature_denial=1

$ ANVAYA LIVE PERSISTED PACKAGE OK sector=2 payload_sector=50 package_bytes=39 client=block-adapter hash_policy=sha256 kernel_fallbacks=0

$ ANVAYA MULTI FRAME STACK OK pid=0xaaa0 pages=2 low_vaddr=0x50030000 high_vaddr=0x50031000 low_paddr=0x80759000 high_paddr=0x8075a000

$ ANVAYA LIVE WASI SERVICE OK service=0xa9d0 app=read-config exit=2 host_grants=1 package_bytes=3459

$ ANVAYA LIVE SDK LAUNCH OK service=0xa9d0 apps=10 profile_derived=1

$ ANVAYA LIVE CATALOG COMPLETE OK service=0xa9d0 apps=12 non_guest=10 guest=2

$ ANVAYA NET RX DISPATCH OK frames=6 arp=1 icmp=1 tcp=1 other_ipv4=1 non_ipv4=1

$ ANVAYA LIVE TCP DATA OK service=0xa9d0 sent=15 acked=15 received=15 denials=1

$ ANVAYA NETWORK SERVICE TASK OK mode=u pid=0xd2c0 net_satp=0x8d2c100000080759 task_generation=0x1701 image_bytes=29997 authority=capability-derived

$ ANVAYA LIVE STORAGE CRATE NAMESPACE OK service=0xa9d0 namespace=/live/config listed=1 object_len=16 denials=1

$ ANVAYA CONTENT STORAGE SERVICE OK mode=u pid=0xd1c0 storage_satp=0x8d1c10000008075b task_generation=0x1601 hash_policy=sha3-256 crdt=lww-tombstone-total

$ ANVAYA CONTENT STORAGE DENIALS OK denials=18 rights=1 wrong_kind_refused_at_ipc=1 wrong_resource=1 wrong_lineage=1 malformed_version=1

$ ANVAYA CONTENT STORAGE PERSISTENCE OK header_lba=128 slot=1 generation=2 persistence=seeded merges_applied=2 recovered_objects=2

$ ANVAYA LIVE AUDIT CONTINUITY OK total=6 success=6 failures=0 last_task=0xa9d0 last_syscall=0x203

$ ANVAYA LIVE IPC DENIAL OK service=0xa9c0 error=bad-handle total=7 failures=1

$ ANVAYA LIVE MEM SYSCALL OK service=0xa9c0 frame=0x1f0010000100000 bytes=4096 satp=0x8a9c10000008075b

$ ANVAYA PRODUCTION ALLOCATOR OK allocated=5 freed=3 reused=2 free_pending=1 denials=3

$ ANVAYA FRAME REFCOUNT OK frame=0x80759000 map_acquired=1 unmap_released=1 shared=3 reclaimed=1 reused=1

$ ANVAYA LIVE TIMER RETRANSMIT OK timer_base=0 deadline_delta=8 attempts=1 timer_sourced=1

$ ANVAYA WASM RICHER OPS OK arith=42 compare=2 div=42 ops=19

$ ANVAYA WASM I64 OK wide_add=1 wide_div=1 width_bits=64 ops=23

$ ANVAYA WASM F32 OK add_eq=1 ieee754=1 ops=11

$ ANVAYA WASM F64 OK add_eq=1 ieee754=1 ops=11

$ ANVAYA WASM CONVERT OK chain=42 uext=9 ops=8

$ ANVAYA WASM MEM WIDE OK i64=42 float=2 ops=6

$ ANVAYA WASM MEM NARROW OK a=4914 b=-1 ops=6

$ ANVAYA WASM EXTERNAL TOOLCHAIN OK compute=63 source=rustc-wasm32 globals=3

$ ANVAYA WASM EXTERNAL CALL OK compute=63 funcs=2 source=rustc-wasm32

$ ANVAYA WASM EXTERNAL LARGE OK compute=154 bytes=261 funcs=3 sig=u16

$ ANVAYA WASM EXTERNAL WASI OK wrote=11 fd=1 source=rustc-wasm32

$ ANVAYA IP ROUTING OK routes=3 on_link=1 specific_lpm=28 default_hop=10.0.2.2 denied=1

$ ANVAYA IP FORWARDING OK neighbors=2 on_link_iface=1 gateway_hop=10.0.2.2 arp_miss=1

$ ANVAYA IP ICMP ECHO OK id=0xa15e seq=9 payload=11 reply_type=0 bad_checksum_denied=1

$ ANVAYA STORAGE SHA256 OK vectors=2 id_bytes=32 deterministic=1 tamper_evident=1

$ ANVAYA STARTUP APP LOADER EXEC OK app=clock-now id=0xff5f93ed35b348fc process=0xa80c code_vaddr=0x40002000 code_bytes=90 checksum=5535

$ ANVAYA VIRTIO DRIVER SERVICE OK mode=u block_pid=0xd150 net_pid=0xd160 block_satp=0x8d15100000080759 block_client_satp=0x8d1410000008076a net_satp=0x8d16100000080853

$ ANVAYA VIRTIO DRIVER RECOVERY OK block_crash_pid=0xd180 block_restart_pid=0xd190 net_restart_pid=0xd1b0 block_old_owner_gen=27 block_new_owner_gen=29 block_old_device_gen=14

$ QEMU boot smoke checks passed.

Real markers from the repeatable boot evidence. Reproduce with ./scripts/check-qemu-boot.sh.

1.8.3

Patch release

Interrupt delivery; SHAKTI target; complete local gates

Rust

Unsafe source measured

syntax spans; includes tests, proof and extensions

NIST

PQC KAT-verified

ML-KEM/ML-DSA/SLH-DSA vs official ACVP vectors

12

Signed WASM proof apps

deny-by-default capability profiles

13

Release gates

workspace, formal, QEMU, driver, storage, network, persistence, platform & monitor

34

milestones on the trajectory

from the 2026-01-01 manifesto to v1.8.3 repair

Trajectory

  1. v0.0.0 · 2026-01-01

    The Manifesto

    The founding document, published before any code: an operating system designed for the age of AI agents, with security, transparency, and sustainability as first principles.

  2. v0.1.0 · 2026-04-20

    First Light

    The kernel boots for the first time — a minimal Rust scaffold coming alive over serial on emulated RISC-V hardware.

  3. v0.2.0 · 2026-05-01

    Permission Is Everything

    Memory isolation goes capability-based — no task touches a page without an explicit, revocable grant — opening a months-long proof train that hardened the model piece by piece.

  4. v0.3.0 · 2026-07-10

    Developer Preview

    The first public cut: signed programs, isolated processes, and working network and storage drivers, every claim asserted by a scripted QEMU boot.

  5. v0.4.0 · 2026-07-11

    Production Substrate

    The kernel becomes dependable: a production program loader, live TCP/IP, disk persistence with cryptographic integrity checks, and a tamper-evident audit trail.

  6. v0.5.0 · 2026-07-13

    AI Agents Move In

    AI agents become native citizens, each running in its own execution context with an identity, explicit goals, granted powers, and a full audit trail.

  7. v0.5.5 · 2026-07-13

    First Silicon in Sight

    Release candidates for real hardware — a reproducible build and strict firmware handoff for the DC-ROMA FML13V01 laptop, with no physical boot claimed until a board proves it.

  8. v0.6.0 · 2026-07-14

    A Constitution for Machines

    Hard rules the system itself must obey: three tiers of constitutional constraints and a human override that software cannot argue with.

  9. v0.7.0 · 2026-07-16

    Quantum-Proof Crypto

    Every trust surface is re-keyed with NIST's post-quantum algorithms, each implementation verified bit-for-bit against the official test vectors.

  10. v0.8.0 · 2026-07-16

    Devices Form a Mesh

    Paired devices share data and delegate powers across machines — every grant cryptographically proven, revocable, and impossible to widen in transit.

  11. v0.9.0 · 2026-07-16

    Made for Humans

    The system meets people: an intent-driven interface, a package manager for signed apps, and an energy broker that meters work in joules and carbon.

  12. v1.0.0 · 2026-07-16

    The QEMU-Proven Milestone

    Feature-complete and formally verified within stated bounds — every claim backed by a reproducible boot log, and everything not yet true said out loud.

  13. v1.1.0 · 2026-07-18

    Back to the North Star

    The code is put back under the manifesto's authority: a machine-checked ledger scores every promise, and a ratchet stops the kernel from quietly growing.

  14. v1.2.0 · 2026-07-19

    Many Cores, Real Time

    The kernel goes multicore with real-time scheduling and asynchronous messaging, retiring the single-processor assumption its proofs had rested on.

  15. v1.3.0 · 2026-08-02

    100× the Monolith

    The 76,824-line main file is distilled to 539 lines as proof code moves behind a compiler-enforced boundary — and the size limit starts tightening itself.

  16. v1.3.1 · 2026-08-02

    100× the Proof Harness

    The proofs get the same treatment, compressing 109-fold into declarative tables while a new oracle demands the boot transcript stay byte-for-byte identical.

  17. v1.3.2 · 2026-08-03

    Proof Bodies Dissolve

    The last hand-written proof code becomes data — 119 proof routines turn into rows run by shared interpreters — and an unreachable stretch target is amended honestly instead of gamed.

  18. v1.3.3 · 2026-08-07

    Truth-Parity Restoration

    A hygiene release: the changelog, status page, and public mirrors are caught up so the published record matches the shipped code again.

  19. v1.3.4 · 2026-08-07

    Version Banner Fix

    A one-line honesty fix: the boot banner stops wearing v1.0.0's old release title beside newer version numbers.

  20. v1.3.5 · 2026-08-07

    The Verifier, Verified

    The self-improvement discipline turns on the proof scripts themselves: 566+ hand-written checks become declarative rows, and the rewrite catches a real bug in the old checks.

  21. v1.3.6 · 2026-08-07

    Honest Accounting

    An audit finds 5,363 kernel lines the size checker never counted; every one is traced, classified, and relocated so nothing sits outside the measurement.

  22. v1.4.0 · 2026-08-07

    The Real Launcher

    Programs can now ask the kernel to launch other programs through a real, permission-checked system call, and every app package carries a post-quantum signature — one size target was missed, and said so.

  23. v1.4.1 · 2026-08-07

    Verify-Only Kernel

    The kernel keeps the power to check signatures but gives up the code to create them, as three subsystems move out — landing below the size target v1.4.0 missed.

  24. v1.5.0 · 2026-08-09

    Driver Domains

    Hybrid-signed virtio-block and virtio-net drivers run as distinct U-mode services with exact device, DMA, IRQ, and IPC authority; QEMU proves persistence, recovery, and opaque-frame reuse without polling or kernel fallbacks.

  25. v1.5.1 · 2026-08-10

    Post-Review Fixes

    Correctness and enforcement fixes from a full post-release review: an IRQ PLIC-source wedge on stale-endpoint interrupts, a dead device-unsafe ratchet, a driver buffer_offset overflow, and a weak-memory used-ring fence. Product core stays 21,834 lines; combined privileged TCB is 23,456.

  26. v1.5.2 · 2026-08-15

    Durable Block Client

    The kernel-private virtio-block client becomes a reusable, capability-scoped adapter. AEC journal/effect/audit and the installer package archive persist through it onto one exclusive proof-disk map; QEMU proves two-boot survival with polling=0 and kernel_fallbacks=0. Product core is 21,870 lines; counted privileged TCB is 23,492.

  27. v1.6.0 · 2026-08-21

    Content-Addressed Storage

    Durable content becomes a userspace service: a signed storage task with its own address space and no device authority owns algorithm-tagged SHA3-256 content addressing, a Kani-proven namespace CRDT, and AVCS A/B recovery through the frozen block client. Product core falls to 20,757 lines and counted privileged TCB to 22,379, with zero storage-service names left in the core. QEMU-proven, and not a production filesystem.

  28. v1.7.0 · 2026-08-27

    Capability Sockets

    A socket becomes a capability with kind, resource identity, rights and generation; the network stack runs as a signed U-mode task that persists its own state, proves five denials and survives death with a fresh generation. Task-composed frames transit a real device interrupt-driven; product core compiles zero network-service names. Socket payloads do not yet leave the machine, so M8 advances DEBT to PARTIAL.

  29. v1.7.1 · 2026-09-05

    Closed-scope repairs

    v1.7.1 closes all 20 findings across the capability, driver, storage, network and verification paths: ancestry-aware revocation, enforced driver rights and DMA quotas, generation-safe sockets, and ABI 0.3 reply tickets. The runtime keeps transport=service-loopback, polling=0 and kernel_fallbacks=0. Product core is 21,530 lines, 23,171 with the transport extension; M1, M6 and M8 stay PARTIAL, QEMU-proven only.

  30. v1.7.2 · 2026-09-25

    Audit repairs and native intelligence

    v1.7.2 closes F01–F19 with native Broker/model recovery and complete local proof. transport=service-loopback, polling=0 and kernel_fallbacks=0 remain; M1, M6 and M8 stay PARTIAL. QEMU-proven, without physical-hardware or external-audit claims.

  31. v1.8.0 · 2026-10-01

    Intelligence and verification maturation

    v1.8.0 completes intelligence and verification maturation: signed userspace Broker/AEC recovery, bounded WASM and shared-runtime capability refinement. transport=service-loopback, polling=0 and kernel_fallbacks=0 remain; M1, M6 and M8 stay PARTIAL. QEMU-proven; physical acceptance and external audit remain pending.

  32. v1.8.1 · 2026-10-06

    Release validation and firmware maintenance

    v1.8.1 maintains the v1.8 research release with constant-space CPU ISA admission, thirteen compiled Lean transport theorems and self-contained pinned ACVP preparation. The selected 8 GiB cap covers both job and aggregate, with zero swap and one job. Fresh exact-source local gates cover all 135 model harnesses, pinned Verus obligations and negative controls, Lean, QEMU, six-boot recovery and four crash cuts, ACVP, accounting and documentation. Signed userspace Broker, model and checkpoint-storage services, bounded WASM and capability refinement retain the v1.8 scope. transport=service-loopback, polling=0 and kernel_fallbacks=0 remain; M1, M6 and M8 stay PARTIAL. v1.9 is deferred with its source and evidence preserved. QEMU-proven research software; physical board acceptance and external audit remain pending.

  33. v1.8.2 · 2026-10-06

    SHAKTI boot readiness

    v1.8.2 adds the shakti-cclass kernel target for a SHAKTI C-class bitstream on a Digilent Arty A7-100T: a SHAKTI UART console, four stated device-tree admission rules for the vendor tree, the SBI TIME timer and a runtime-probed escape. On QEMU shakti_c it reaches first light under OpenSBI v1.7 and, under the Rust machine-mode resident monitor, runs the signed hello-status app and fires the PMP-gated escape; read-only probes and a private loading kit went to IIT Madras. SHAKTI is Buildable with no physical boot claimed. v1.8.2 was tagged and released on GitHub under an owner-amended proof scope and was not deployed to anvaya.dev; v1.8.3 carries it forward with the complete local proof.

  34. v1.8.3 · 2026-10-08

    Interrupt-delivery repair

    v1.8.3 fixes the intermittent qemu-virt boot hang present since before v1.8.2: a device interrupt taken while a client or service runs in user mode is now claimed through the bare kernel map, fatal reports print through it, and a restarted driver binding drains the PLIC source its predecessor left latched. v1.8.2 added the shakti-cclass kernel target for a SHAKTI C-class bitstream (Buildable, QEMU shakti_c only), with OpenSBI and Rust machine-mode monitor lanes and a private loading kit for IIT Madras. Fresh exact-source local gates at the v1.8.3 tag cover all 135 model harnesses, pinned Verus obligations and negative controls, Lean, QEMU with both SHAKTI lanes, six-boot recovery and four crash cuts, ACVP, accounting and documentation. transport=service-loopback, polling=0 and kernel_fallbacks=0 remain; M1, M6 and M8 stay PARTIAL. v1.9 is deferred with its source and evidence preserved. QEMU-proven research software; physical board acceptance and external audit remain pending.

Proof-Driven Engineering

METHOD

No roadmap slideware. Each increment lands with focused code, unit tests, and QEMU boot markers checked by release gates — from capability attenuation to two-boot storage persistence.

Capability Boundaries

SECURITY

Every kernel object is reached through explicit, attenuable, revocable capabilities with lineage tracking. Denial paths are proved with the same rigor as success paths.

AI-Native Target

DIRECTION

The target state is an OS built for agentic workloads: bounded execution, explicit authority, human override, and audit-ready transparency from the nucleus up.

Manifesto

DOC-001

The ANVAYA Manifesto lays out the first principles of the Intelligence Age operating system: AI-native execution, capability security, post-quantum cryptography, and sustainable computing at planetary scale.

Open ManifestoView on GitHub

Implementation Status

STATUS

Honest, area-by-area maturity: what is evidence-backed prototype, what is accepted specification, and what remains future work.

Open Status

Changelog

UPDATES

Every verified release, from first light to the sret-continue dispatcher slice, with the exact proof markers each one added.

View Updates

Docs Index

DOCS

Canonical references, policies, methodology, and machine-readable assets for AnvayaOS.

Open Docs

Get Involved

JOIN

ANVAYA is built in the open. We are looking for sponsors, individuals and organisations alike, and for contributors: software developers, RISC-V hardware developers, RISC-V chip designers and fabs, verification and cryptography researchers, AI-systems and alignment researchers, and writers.

Both forms reach a person at info@anvaya.dev and send you a confirmation copy. No account, no trackers.

Sponsor ANVAYAContributeGitHub