╔═╗╦═╗╦ ╦╔═╗╦  ╔═╗╔╦╗╔═╗╦═╗
 ╚═╗╠╦╝║ ║╠═╣║  ╠═╣ ║ ║ ║╠╦╝
 ╚═╝╩╚═╚═╝╩ ╩╩═╝╩ ╩ ╩ ╚═╝╩╚═

the best computation substrate if you started from scratch — agent-native, capability-based, content-addressed, deterministic, observable.

exploratory hardware sketch · source-backed runtime proposal · wire


Not an implemented or verified architecture. This earlier hardware sketch remains speculative. The revised stack starts on existing hardware and defines authority, replay, effects, and failure tests. Instruction encodings, capability compression, revocation, concurrency semantics, and performance need a formal specification and experiments before implementation.

0. design principles

six rules, in priority order. everything below follows from these.


1. instruction set (the wire ISA)

RISC-V's clean design, simplified further. 32-bit fixed instructions, 4-byte aligned, load-store architecture.

registers

instruction formats (4 types, all 4 bytes)

4 types instead of 6 (RISC-V has 6). simpler decoder. no B-type or J-type (branches use I-type with PC-relative offset, jumps use U-type + I-type).

core instructions (~40, not 100+)


2. capability system (the security substrate)

CHERI-inspired. every pointer is a capability. no ambient authority. hardware-enforced.

capability fields (224 bits plus a validity tag, uncompressed)

tag bit is the key: a capability is only valid if its tag bit is 1. any write to a capability register or memory location clears the tag. you cannot forge a capability by writing to memory — the tag bit is set only by the hardware on capability operations.

capability operations

capability rules (hardware-enforced)


3. memory model (the storage substrate)

flat 64-bit, page-based virtual memory, tagged, content-addressable.

address space

content-addressable storage

memory ordering


4. concurrency substrate

atomic operations, transactional memory, lock-free data structures.

atomic operations

hardware transactional memory (HTM)


5. agent-native I/O

capability-gated, structured, self-describing, versioned.

I/O model

I/O channels (capabilities)


6. observability (the debugging substrate)

built-in tracing, deterministic replay, self-describing execution.

tracing

deterministic replay


7. what we left out (and why)

every omission is a deliberate choice.


8. comparison with existing architectures

what we took from each, and what we rejected.


This sketch is a proposal, not a consequence proven by the corpus. See the revised stack for primary sources, explicit boundaries, and acceptance experiments.