Reading paths, featured documents and areas
Featured now
11
The docs most closely tied to the current implementation and architecture cleanup.
design · AstraReaktor Product AtlasOne engine across the software lifecycle: persistent source and Blueprint editors, full-stack modules, actors, capabilities, FFI, cloud placement, AI harnesses, devices, releases, telemetry and analytics. Every Pencil board, with implementation handoffs and explicit design status.
start here · AstraAstra Reaktor Plan and RoadmapIdea to design to working app, powered by Claude/Codex and a composable runtime. The refined core—live graphs, actors, capabilities, FFI and formal methods—plus December 2026 v1 and the two-developer roadmap.
master planDesktop Master PlanThe combined constitution and build score for Reaktor Desktop: product laws, Graph Studio and System Fabric architecture, the verified state of every surface, a decision log, trust and delivery gates, and six shippable phases — two independent plans merged into one readable document.
overviewFramework OverviewThe single holistic overview for beginners and experts: the full-stack-modules + Turing-complete-wiring model, the Unreal Engine analogy, the graph and its visitors, a real BestBuds worked example, and every subsystem — with an honest shipped-vs-designed map.
moduleService LayerGraph-neutral service contracts: typed Request/Response DTOs, handlers, endpoint identity, staged OkHttp-style interceptors, HTTP adapters, connection setup hooks, Cloudflare service bindings, ServiceNode projection, and the boundary to bus, queue, pubsub, and workflow delivery.
securityAuth ArchitectureSource of truth for Reaktor auth: graph runtime, AuthContext, anonymous guest sessions, Supabase email/password, magic links, OTP, provider exchange, sessions, PATs, service accounts, Worker verification, schema, and E2E gates.
performanceHigh-Performance FlexBufferThe complete runtime guide: generated and raw kotlinx tiers, every retained optimization, JVM/ART/Native/JS/C++ evidence, BestBuds and Manna adoption, and versioned low-copy FFI design.
opsCloud Control PlaneGCP-first cloud control plane for regional k3s cells: Reaktor-managed capacity billed through Reaktor, customer-owned GCP cells managed through reaktor-agent, typed fleet operations, Dagger/Pulumi execution, and no scattered provider auth or Node sidecar.
control-planeUnified GraphThe canonical heterogeneous, nested, multilayer port graph: source, build and runtime identities; composition, execution profiles, visitors, graph changes and AI.
architectureFormal MethodsHow an application built inside Reaktor's semantic boundary inherits machine-checked guarantees, and how verification results flow back to coding agents as structured counterexamples instead of failing tests.
control-planeConductorDrive Claude Code and Codex from inside Reaktor: your own agents, your own collaboration topologies, and one canonical conversation that outlives either tool.
Choose a reading path
6
Six routes through the catalog, each written for a different reason to be here. Every path is three to five documents, in order.
Start here
7
Find your reading path, understand Reaktor's purpose and direction, then use the contributor guide to start work. Begin with the documentation library or Framework Overview.
Documentation library and improvement programmeguide · Reaktor documentationReading paths for people, retrieval systems and agents; source coverage, audit criteria, website improvements and remaining editorial work.7 min read
Reaktor Framework Overviewoverview · ClaudeThe single holistic overview for beginners and experts: the full-stack-modules + Turing-complete-wiring model, the Unreal Engine analogy, the graph and its visitors, a real BestBuds worked example, and every subsystem — with an honest shipped-vs-designed map.35 min read
Reaktor Essays — Two Readingsoverview · Claude + CodexTwo independent technical essays written to the same brief without either author seeing the other's work: Claude (Fable 5) argues from what a live runtime graph makes possible, Codex argues from what a small trusted semantic kernel makes provable. Both are reproduced verbatim.14 min read
Astra Reaktor Plan and Roadmapstrategy · Astra / CodexReaktor's software-forge north star: create and evolve apps with a live graph, actors, capabilities, polyglot FFI, formal methods and Claude/Codex; current system status and a two-developer roadmap to December 2026 public v1 and September 2027.1.6 hr read
Contributing to Reaktorguide · MergedThe practical entry point for a new contributor: what lives in which repository, the module map, how to set up and build, the two rules every module must obey, where to put a change, and how to add or edit a doc on this site.8 min read
Documentation audit — 7 October 2026analysis · Reaktor documentationCriterion-by-criterion findings across the public and private corpus, source integration, structural repairs, canonical roles and editorial priorities.10 min read
Markdown graph markersguide · Reaktor documentationAuthor document metadata, navigation regions, named ports and relationships in Markdown; generate every graph and reading view from the same declarations.5 min read
Theory and worked designs
18
Start with the graph model and Kotlin language, then inspect thirty designs with named ports, hyperedge roles and explicit runtime qualifications.
Explore 18 documents in Theory and worked designs
Architecture atlas
8
The October design synthesis: invariants, vocabulary, semantics, lowering, releases, precedents and concrete scenarios. Read as design, with current implementation evidence in module chapters.
Explore 8 documents in Architecture atlas
Engine reference
10
The September technical preprint as an ordered web book. Scope and source lineage remain explicit; current guides own implementation status.
Explore 10 documents in Engine reference
Data layer
12
One ordered home for data architecture, storage, tenancy, transactions, durable delivery, live channels, execution, inspection and qualification.
Explore 12 documents in Data layer
Using the framework
23
The modules you build an application out of: what each one gives you, the API it exposes, and how far it is actually built.
Explore 23 documents in Using the framework
FlexBuffers and FFI
19
Binary wire formats, measured codec performance and stability, mutable-memory design, and ownership across language boundaries.
Explore 19 documents in FlexBuffers and FFI
The graph model
14
Reaktor's central idea: an application is a typed graph. These docs define the kernel, what walks it, how it runs, and what can be proved about it.
Explore 14 documents in The graph model
Build and ship
8
The toolchain, deployment and fleet resources that take a working change into production. Operations & Reliability owns diagnostics and verification.
Explore 8 documents in Build and ship
Operations & Reliability
23
Shared observability, instance health, profiling, realistic load and the Shadow textbook: evidence from graph and source to a repeatable experiment.
Explore 23 documents in Operations & Reliability
Workbench
9
The surfaces people use to see and change a running system: the desktop workbench, its panes and the visual language. Agent tooling has its own group.
Explore 9 documents in Workbench
Agents
8
Everything about AI agents and Reaktor: how agents build Reaktor code cheaply, the control plane agents call, how Reaktor drives Claude Code and Codex, and the agents that run inside Reaktor products and tools.
Explore 8 documents in Agents
Products built on Reaktor
6
Real applications on the framework. They are the honesty check: anything the framework claims has to survive one of these.
Explore 6 documents in Products built on Reaktor
Background and archive
16
Kept for the record: market positioning, adversarial reviews, superseded plans, and long research dumps. Nothing here is current — read it for how a decision was reached, not for what is true now.
Explore 16 documents in Background and archive