# Reaktor Documentation

> Design briefs, architecture, runtime modules, operations and product docs for Reaktor, a Kotlin Multiplatform framework that treats a full-stack application as one typed graph. 181 documents, 2362 declared relationships between them. Updated 2026-10-07.

Machine-readable: the knowledge graph (every document, its metadata, and explicit ports and relationships between documents) is JSON at https://reaktor.build/docs/graph.json, and every document's section headings are at https://reaktor.build/docs/outline.json.

Each document states its own status. Where a doc and the source disagree about what exists today, the source is right.

## Start here

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 programme](https://reaktor.build/docs/documentation-library) (2026-10-08, 7 min): Reading paths for people, retrieval systems and agents; source coverage, audit criteria, website improvements and remaining editorial work.
- [Reaktor Framework Overview](https://reaktor.build/docs/reaktor-framework-overview) (2026-10-08, 35 min): The 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.
- [Reaktor Essays — Two Readings](https://reaktor.build/docs/reaktor-essays) (2026-10-08, 14 min): Two 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.
- [Astra Reaktor Plan and Roadmap](https://reaktor.build/docs/astra-reaktor-plan-and-roadmap) (2026-10-08, 99 min): Reaktor'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.
- [Contributing to Reaktor](https://reaktor.build/docs/contributing) (2026-10-08, 8 min): The 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.
- [Documentation audit — 7 October 2026](https://reaktor.build/docs/documentation-audit) (2026-10-08, 10 min): Criterion-by-criterion findings across the public and private corpus, source integration, structural repairs, canonical roles and editorial priorities.
- [Markdown graph markers](https://reaktor.build/docs/documentation-graph-markers) (2026-10-08, 5 min): Author document metadata, navigation regions, named ports and relationships in Markdown; generate every graph and reading view from the same declarations.

## Theory and worked designs

Start with the graph model and Kotlin language, then inspect thirty designs with named ports, hyperedge roles and explicit runtime qualifications.

### Theory

- [Reaktor graph theory — the model and its boundaries](https://reaktor.build/docs/reaktor-graph-theory) (2026-10-08, 8 min): Typed nested port hypergraphs, identity/revision/activation, open dialects, composition and implementation boundaries.
- [Nodes](https://reaktor.build/docs/reaktor-graph-vocabulary-theory) (2026-10-08, 149 min): Nodes: task designs, behavior classes, compositions and domain roles.
- [Ports](https://reaktor.build/docs/reaktor-port-theory) (2026-10-08, 83 min): Ports: task designs, protocol modes, ownership dimensions and contract profiles.
- [Hyperedges](https://reaktor.build/docs/reaktor-hyperedge-theory) (2026-10-08, 133 min): Hyperedges: task designs, relation laws, constraints and compositions.
- [Nested graphs](https://reaktor.build/docs/reaktor-nested-graphs-theory) (2026-10-08, 16 min): Nested graphs: 5 diagrammed designs, with legends, domains, Reaktor examples and explicit laws.
- [Subgraph views, visitors and traversals](https://reaktor.build/docs/reaktor-graph-views-theory) (2026-10-08, 24 min): Subgraph views, visitors and traversals: 5 diagrammed designs, with legends, domains, Reaktor examples and explicit laws.
- [The Reaktor graph language — Kotlin common DSL and arbitrary logic](https://reaktor.build/docs/reaktor-graph-language-theory) (2026-10-08, 5 min): Graph declarations plus arbitrary common Kotlin, ordinary KMP interoperability, Kotlin/JS lowering, graph/system access and qualified FFI.
- [Graph composition, distribution and safe change](https://reaktor.build/docs/reaktor-graph-distribution-theory) (2026-10-08, 4 min): Execution profiles, graph cuts, authority-mediated changes, code push, epochs, migration, draining and evidence.
- [Graph model precedents and their limits](https://reaktor.build/docs/reaktor-graph-precedents) (2026-10-08, 3 min): Primary sources for Kotlin DSLs, open-system composition, MLIR and dataflow scheduling with explicit scope and inference.
- [Reaktor system atlas](https://reaktor.build/docs/reaktor-system-atlas) (2026-10-08, 2 min): Thirty interactive representative designs using the same Blueprint renderer and shared theme as Manna Atlas.

### Worked designs

- [Mobile apps — worked graph designs](https://reaktor.build/docs/reaktor-examples-mobile) (2026-10-08, 29 min): 5 worked mobile apps designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Websites — worked graph designs](https://reaktor.build/docs/reaktor-examples-web) (2026-10-08, 27 min): 5 worked websites designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Distributed systems — worked graph designs](https://reaktor.build/docs/reaktor-examples-distributed) (2026-10-08, 27 min): 5 worked distributed systems designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Bolt-on capabilities — worked graph designs](https://reaktor.build/docs/reaktor-examples-capabilities) (2026-10-08, 36 min): 7 worked bolt-on capabilities designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Workflows — worked graph designs](https://reaktor.build/docs/reaktor-examples-workflows) (2026-10-08, 10 min): 2 worked workflows designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Multiplayer games — worked graph designs](https://reaktor.build/docs/reaktor-examples-games) (2026-10-08, 11 min): 2 worked multiplayer games designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [Robotic fleets — worked graph designs](https://reaktor.build/docs/reaktor-examples-robotics) (2026-10-08, 10 min): 2 worked robotic fleets designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.
- [IoT — worked graph designs](https://reaktor.build/docs/reaktor-examples-iot) (2026-10-08, 11 min): 2 worked iot designs with port profiles, hyperedge roles, arbitrary Kotlin logic and explicit failure conditions.

## Architecture atlas

The October design synthesis: invariants, vocabulary, semantics, lowering, releases, precedents and concrete scenarios. Read as design, with current implementation evidence in module chapters.

- [Architecture thesis and invariants](https://reaktor.build/docs/architecture-atlas-foundations) (2026-10-08, 25 min): Astra architecture synthesis: architecture thesis and invariants. Design claims and falsifiable acceptance obligations.
- [Nodes, ports and hyperedge vocabulary](https://reaktor.build/docs/architecture-atlas-vocabulary) (2026-10-08, 67 min): Astra architecture synthesis: nodes, ports and hyperedge vocabulary. Design claims and falsifiable acceptance obligations.
- [Composition and execution semantics](https://reaktor.build/docs/architecture-atlas-semantics) (2026-10-08, 15 min): Astra architecture synthesis: composition and execution semantics. Design claims and falsifiable acceptance obligations.
- [Compiler, source publication and consistency](https://reaktor.build/docs/architecture-atlas-language) (2026-10-08, 13 min): Astra architecture synthesis: compiler, source publication and consistency. Design claims and falsifiable acceptance obligations.
- [Shadow, evidence and region releases](https://reaktor.build/docs/architecture-atlas-evolution) (2026-10-08, 14 min): Astra architecture synthesis: shadow, evidence and region releases. Design claims and falsifiable acceptance obligations.
- [Authoring and industry precedents](https://reaktor.build/docs/architecture-atlas-workbench) (2026-10-08, 9 min): Astra architecture synthesis: authoring and industry precedents. Design claims and falsifiable acceptance obligations.
- [Cross-runtime systems and worked scenarios](https://reaktor.build/docs/architecture-atlas-scenarios) (2026-10-08, 44 min): Astra architecture synthesis: cross-runtime systems and worked scenarios. Design claims and falsifiable acceptance obligations.
- [Impact, design obligations and qualification](https://reaktor.build/docs/architecture-atlas-qualification) (2026-10-08, 38 min): Astra architecture synthesis: impact, design obligations and qualification. Design claims and falsifiable acceptance obligations.

## Engine reference

The September technical preprint as an ordered web book. Scope and source lineage remain explicit; current guides own implementation status.

- [The engine and feature composition](https://reaktor.build/docs/engine-preprint-engine) (2026-10-08, 35 min): September technical preprint: the engine and feature composition. Historical design and explicitly scoped evidence.
- [Graph model, protocols and computation](https://reaktor.build/docs/engine-preprint-graph) (2026-10-08, 47 min): September technical preprint: graph model, protocols and computation. Historical design and explicitly scoped evidence.
- [Platforms, identity and polyglot execution](https://reaktor.build/docs/engine-preprint-runtime) (2026-10-08, 23 min): September technical preprint: platforms, identity and polyglot execution. Historical design and explicitly scoped evidence.
- [Data authority, contracts and federation](https://reaktor.build/docs/engine-preprint-data) (2026-10-08, 12 min): September technical preprint: data authority, contracts and federation. Historical design and explicitly scoped evidence.
- [Build, compilation and resource budgets](https://reaktor.build/docs/engine-preprint-delivery) (2026-10-08, 16 min): September technical preprint: build, compilation and resource budgets. Historical design and explicitly scoped evidence.
- [LiveUpdate, coordinator and human-agent authoring](https://reaktor.build/docs/engine-preprint-evolution) (2026-10-08, 26 min): September technical preprint: liveupdate, coordinator and human-agent authoring. Historical design and explicitly scoped evidence.
- [Assurance and adoption studies](https://reaktor.build/docs/engine-preprint-assurance) (2026-10-08, 37 min): September technical preprint: assurance and adoption studies. Historical design and explicitly scoped evidence.
- [Precedents, evaluation and implementation sequence](https://reaktor.build/docs/engine-preprint-evaluation) (2026-10-08, 16 min): September technical preprint: precedents, evaluation and implementation sequence. Historical design and explicitly scoped evidence.
- [References, notation, exercises and source lineage](https://reaktor.build/docs/engine-preprint-reference) (2026-10-08, 31 min): September technical preprint: references, notation, exercises and source lineage. Historical design and explicitly scoped evidence.
- [Engine preprint: original page layouts](https://reaktor.build/docs/engine-preprint-facsimile) (2026-10-08, 236 min): All 114 source pages as web vector images with extracted text, preserving exact original typography without requiring the PDF.

## Data layer

One ordered home for data architecture, storage, tenancy, transactions, durable delivery, live channels, execution, inspection and qualification.

### Architecture and model

- [Tidemark — Reaktor Data Layer](https://reaktor.build/docs/reaktor-db) (2026-10-08, 31 min): Full data infrastructure within the main Reaktor graph: SQL-first datastore families, typed Service/FFI contracts, querying, consistency, sync, pubsub/queues, realtime, lifecycle, portability and scaling.
- [The Data Graph — data within Reaktor's unified graph](https://reaktor.build/docs/reaktor-data-graph) (2026-10-08, 12 min): Logical entities, datasets, access patterns, operations and physical bindings in the canonical typed heterogeneous multiplex port graph; semantic links, query plans, lineage, lifecycle and evidence.
- [Data Storage — Current APIs and Platform Boundaries](https://reaktor.build/docs/reaktor-data-storage) (2026-10-08, 5 min): Source-grounded persistence APIs, browser SQLite/OPFS migration, graph policies and snapshot-transfer limits.

### Scope and state

- [Reaktor Multitenancy — one ambient scope, enforced everywhere](https://reaktor.build/docs/reaktor-multitenancy) (2026-10-08, 29 min): Tenancy as a cross-cutting concern done once, not per query: ambient AuthContext.tenantId, enforced store adapters, pool/bridge/silo policy, Reaktor-managed GCP cells, customer-owned GCP cells, per-tenant actors/DOs, cells + shuffle-sharding, residency, quotas, and lifecycle operations.
- [Transactions, Ledgers and Derived State](https://reaktor.build/docs/reaktor-data-transactions) (2026-10-08, 10 min): Caching, batching, ledgers, state machines, reconciliation, outbox admission, sagas and projection positions.

### Delivery and execution

- [Reaktor Bus](https://reaktor.build/docs/reaktor-bus-mesh) (2026-10-08, 21 min): Source of truth for Reaktor's durable async delivery fabric: typed envelopes, routing, GCP Pub/Sub, Cloudflare Queues, outbox, idempotent consumers, DLQ, replay, graph projection, and the boundary to service, work, mesh, and distributed actors.
- [Reaktor Mesh](https://reaktor.build/docs/reaktor-mesh) (2026-10-07, 12 min): Source of truth for Reaktor's live connectivity layer: peer sessions, WebRTC, Cloudflare TURN credential issuance, Cloudflare Realtime SFU sessions/tracks/DataChannels, graph projection, and the handoff to Bus for durable facts.
- [Durable Jobs — Cloudflare Queues and Workflows](https://reaktor.build/docs/reaktor-data-workflows) (2026-10-08, 9 min): Durable admission, idempotent effects, checkpointed execution and current/proposed adoption across Reaktor, Manna and BestBuds.
- [Reaktor Work](https://reaktor.build/docs/reaktor-work) (2026-10-09, 44 min): Meeseeks replacement design, diagrams and Reaktor reuse audit: graph-owned WorkStore, WorkRuntime and WorkScheduler, native durable coordination, typed DAGs, retained journals and reference-engine feature comparison. Implementation remains experimental.

### Inspection and qualification

- [Data Inspection — Authority, Providers and Query Receipts](https://reaktor.build/docs/reaktor-data-inspection) (2026-10-08, 11 min): Provider views, SQL authority profiles, bounded query receipts and remaining operator qualification.
- [Data Implementation, Qualification and Sources](https://reaktor.build/docs/reaktor-data-implementation) (2026-10-08, 7 min): Staged evidence gates, lifecycle obligations, preprint coverage and the canonical/retired document register.
- [BestBuds Public and Heimdall Schema Hardening](https://reaktor.build/docs/bestbuds-schema-hardening) (2026-10-08, 16 min): Performance, correctness, transaction, and scalability plan for replacing the broad BestBuds public compatibility views over Heimdall with app-scoped projections, alias tables, bounded chat queries, atomic refresh rotation, schema drift checks, and grant/RLS hardening.

## Using the framework

The modules you build an application out of: what each one gives you, the API it exposes, and how far it is actually built.

### Module assessment and execution

- [Reaktor Module Execution Plan — Delivering the Astra Vision](https://reaktor.build/docs/reaktor-module-execution-plan) (2026-10-11, 70 min): Five ranked tasks for each of 69 module/build/target units, plus 11 supporting systems: 400 task entries with Astra traceability, prerequisites, acceptance evidence and December, year-one or conditional horizons.
- [Reaktor Module Review — Readiness, Graph Integration and Compounding Value](https://reaktor.build/docs/reaktor-module-review) (2026-10-11, 85 min): Source-grounded assessment of all 37 open Reaktor directories, five closed library slices, 27 targets and supporting systems: purpose, quality, stability, usage, vision, impact and typed multilayer graph integration.

### Foundations

- [reaktor-capability](https://reaktor.build/docs/reaktor-capability) (2026-10-08, 12 min): Environment snapshots, capability profiles, strategy selection, and degradation tiers.
- [Reaktor Core — the foundation layer](https://reaktor.build/docs/reaktor-core) (2026-10-08, 17 min): The foundation every module imports: the Feature slot registry (kills every 'is this Android?' branch), the Capability AutoCloseable resource marker, the WeakRef Adapter platform bridge, and cross-platform primitives (time/dispatchers/logging/atomics/serialization) — plus how the designed capability runtime (normalized device/network tiers) installs on it via a Feature slot. Disambiguates the four meanings of 'capability'.
- [Reaktor Service](https://reaktor.build/docs/reaktor-service) (2026-10-08, 12 min): Current typed HTTP handlers and the proposed unified Service contracts: sync, async, streams, duplex, publication/subscription and durable jobs, with qualified FFI and runtime bindings.

### Auth and backend

- [Reaktor Auth](https://reaktor.build/docs/auth-analysis) (2026-10-08, 66 min): Source 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. Includes a general-purpose design review (§25–§30): the auth-landscape comparison, the tenant-vs-context unified-scope proposal, the first-party credential/MFA design, graph amplification, and a STRIDE/compliance/DX/performance review. §31 adds the Google/Apple OAuth authorization design: provider grants, server-side code exchange, refresh, and Apple-required revocation.
- [Deep Link Integration](https://reaktor.build/docs/deep-link-integration) (2026-10-08, 17 min): Graph-native URI model, route index, backstack planner, guards, and platform bridges.
- [Reaktor Notifications](https://reaktor.build/docs/reaktor-notifications-design) (2026-10-08, 50 min): Cloudflare-native notification runtime with D1 operational state, Workers/Durable Objects/Queues, FCM delivery from Cloudflare, reaktorServer-issued access tokens, client adapters, graph routing, telemetry, and workbench operations.
- [Reaktor Server — production backend primitives](https://reaktor.build/docs/reaktor-server) (2026-10-08, 40 min): The production discipline layer for command-shaped APIs, invariants, state machines, ledgers, reconciliation, idempotency, retries, circuit breakers, queues, outbox, CQRS, saga, and event sourcing — mapped onto reaktor-graph (interceptors/facets/actors/bus) and run on Spring Boot (JVM/k3s) and Cloudflare Workers (edge).

### Reaktor Surface

- [Reaktor Surface](https://reaktor.build/docs/reaktor-surface) (2026-10-08, 3 min): The Surface textbook: component meaning and behavior, Graph ownership, Compose Multiplatform and React web and Compose renderers, adaptive layout, motion, performance, dynamic UI, and application patterns.
- [Application extensions](https://reaktor.build/docs/reaktor-surface-application-extensions) (2026-10-08, 7 min): Chapters 31–33: commerce, creative software, and accessibility.
- [Application patterns](https://reaktor.build/docs/reaktor-surface-application-patterns) (2026-10-08, 12 min): Chapters 27–30: BestBuds, workbenches, media, and communication.
- [Contracts and interaction](https://reaktor.build/docs/reaktor-surface-contracts-and-interaction) (2026-10-08, 17 min): Chapters 7–10: contracts, behavior, events, interaction, and input.
- [Design and ownership](https://reaktor.build/docs/reaktor-surface-design-and-ownership) (2026-10-08, 21 min): Chapters 11–14: atomic design, state ownership, themes, and adaptive layout.
- [Desktop](https://reaktor.build/docs/reaktor-surface-desktop) (2026-10-08, 32 min): Chapters 35–37: focus, keys, overlays, menus, commands, density and cost, then collections, panes, tab sets, notices and islands on the desktop.
- [Dynamic UI and verification](https://reaktor.build/docs/reaktor-surface-dynamic-ui-and-verification) (2026-10-08, 9 min): Chapters 24–26: graph updates, specialized interfaces, and verification.
- [Foundations](https://reaktor.build/docs/reaktor-surface-foundations) (2026-10-08, 26 min): Chapters 1–6: interface challenges, concepts, architecture, platforms, and a Send action.
- [Implementation plan](https://reaktor.build/docs/reaktor-surface-implementation-plan) (2026-10-08, 10 min): Chapter 34: a staged Compose-first implementation plan.
- [Motion and materials](https://reaktor.build/docs/reaktor-surface-motion-and-materials) (2026-10-08, 14 min): Chapters 18–20: animation, tactile response, and material effects.
- [Performance and assets](https://reaktor.build/docs/reaktor-surface-performance-and-assets) (2026-10-08, 12 min): Chapters 21–23: scheduling, memory, images, and delivery.
- [References](https://reaktor.build/docs/reaktor-surface-references) (2026-10-08, 3 min): Sources and further reading for the Surface textbook.
- [Renderers and interop](https://reaktor.build/docs/reaktor-surface-renderers) (2026-10-08, 13 min): Chapters 15–17: Compose, React, and renderer boundaries.
- [Reaktor WebView runtime plan](https://reaktor.build/docs/reaktor-webview) (2026-10-08, 10 min): System WebViews across Android, iOS, desktop and browser targets, packaged web tools, graph bridge security and Hangar migration from JCEF.

## FlexBuffers and FFI

Binary wire formats, measured codec performance and stability, mutable-memory design, and ownership across language boundaries.

### FlexBuffers

- [FlatBuffers and FlexBuffers: From Bytes to Mutable Memory](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory) (2026-10-08, 9 min): Reading map for the complete supplied 127-page first edition: 30 chapters, 32 exercises, seven appendices, 14 tables, worked wire examples, all 778 printed C++ source lines and 25 primary-source links. Five part pages and seven appendix pages preserve the complete text and source; LiveFlex remains distinct from current Reaktor implementation.
- [Part I Bytes and Ownership](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-01-bytes-and-ownership) (2026-10-08, 12 min): Representations, scalar layout, alignment, arithmetic, and safe C++ byte views.
- [Part II FlatBuffers](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-02-flatbuffers) (2026-10-08, 23 min): Tables, vtables, structs, vectors, builders, schema evolution, verification, and constrained mutation.
- [Part III FlexBuffers](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-03-flexbuffers) (2026-10-08, 36 min): The trailer, width solver, strings, vector families, maps, views, builders, mutation, and verification.
- [Part IV Quality and Performance](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-04-quality-and-performance) (2026-10-08, 19 min): Interoperability, hardware, language boundaries, workload-normalized benchmarks, and earned optimizations.
- [Part V LiveFlex Mutable Memory](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-05-mutable-memory) (2026-10-08, 33 min): Compatibility, cells, descriptors, allocation, reclamation, containers, transactions, snapshots, and staged delivery.
- [Appendix A Type Codes and Byte Equations](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-06-appendix-a) (2026-10-08, 5 min): Type Codes and Byte Equations from the complete supplied first edition.
- [Appendix B Exercise Solutions and Implementation Hints](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-07-appendix-b) (2026-10-08, 9 min): Exercise Solutions and Implementation Hints from the complete supplied first edition.
- [Appendix C Reading the Official Implementation](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-08-appendix-c) (2026-10-08, 5 min): Reading the Official Implementation from the complete supplied first edition.
- [Appendix G Sources and Edition Notes](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-12-appendix-g) (2026-10-08, 4 min): Sources and Edition Notes from the complete supplied first edition.
- [Reaktor FlexBuffer — High-Performance Binary Serialization](https://reaktor.build/docs/flexbuffer-implementation) (2026-10-08, 51 min): Current implementation and adoption guide: generated/raw/accessor/caller-owned tiers, platform kernels, October correctness blockers, historical July evidence, wire and allocation tradeoffs, ownership, schema safety, and proposed native/compiler/mutable-memory work.
- [FlexBuffer Improvement Plan](https://reaktor.build/docs/flexbuffer-improvement-plan) (2026-10-08, 1 min): Earlier FlexBuffer optimization plan, superseded by the implementation ledger.
- [FlexBuffers: October performance and stability review](https://reaktor.build/docs/flexbuffer-performance-review) (2026-10-08, 15 min): October source-grounded measurements on M4 Pro, actual Chrome and physical S23 Ultra/iPhone 14 Pro: JSON, kotlinx ProtoBuf and packed Google Java Protobuf, allocations, wire sizes, partial reads, validation, Android bulk experiments, four unresolved correctness defects and prioritized optimization gates.
- [Appendix D Checked FlexBuffers Laboratory](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-09-appendix-d) (2026-10-07, 10 min): Checked FlexBuffers Laboratory from the complete supplied first edition.
- [Appendix E Mutable Semantic Laboratory](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-10-appendix-e) (2026-10-07, 5 min): Mutable Semantic Laboratory from the complete supplied first edition.
- [Appendix F FlatBuffers Table Laboratory](https://reaktor.build/docs/flatbuffers-flexbuffers-mutable-memory-11-appendix-f) (2026-10-07, 2 min): FlatBuffers Table Laboratory from the complete supplied first edition.

### FFI

- [Kotlin/CLR — a .NET backend for Kotlin](https://reaktor.build/docs/kotlin-clr) (2026-10-08, 47 min): A Kotlin compiler backend emitting CIL and ECMA-335 metadata: an importer that reads assembly metadata lazily in the frontend the way Kotlin reads Java, a two-process emitter that can host Roslyn, a single CLR-shaped member set, the type-mapping decision table including the cases that do not map (struct value classes, enums in both directions, ByteArray, iterator protocols), suspend over Task without losing structured concurrency, reflection-free metadata for IL2CPP and NativeAOT, NuGet and MSBuild packaging as the adoption bottleneck, the coroutines and serialisation ports the target requires, and a first milestone that is a hand-written CIL conformance corpus.
- [Reaktor FFI — Switchboard, the universal language bridge](https://reaktor.build/docs/reaktor-ffi) (2026-10-08, 24 min): Current native hello proof and transport TODOs, plus proposed Switchboard typed frames, cross-language Flow, C ABI, graph representation, buffer ownership, mutable-runtime design input and acceptance gates. Refreshed against October codec failures; no production frame/hop latency is measured.
- [Reaktor Switchboard — the FFI design](https://reaktor.build/docs/reaktor-ffi-design) (2026-10-08, 1 min): Merged into the canonical Reaktor FFI document.

## The graph model

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.

### Kernel and runtime

- [Graph Kernel Analysis](https://reaktor.build/docs/graph-kernel-analysis) (2026-10-08, 16 min): Universal composition kernel for graph runtime, modules, visitors, snapshots, and commands.
- [Reaktor Graph Visitors](https://reaktor.build/docs/reaktor_graph_visitors_design) (2026-10-08, 19 min): Routing, wiring, deep links, auth, analytics, workflow compilation, export, validation, and debugging as graph passes.
- [Reaktor Actor Model](https://reaktor.build/docs/reaktor-actor-model) (2026-10-08, 9 min): ActorNode as a graph node with a serialized mailbox, exclusive state, and port wiring.
- [Reaktor Distributed Actors](https://reaktor.build/docs/reaktor-distributed-actors) (2026-10-08, 28 min): Location-transparent actors across k3s JVM pods and Cloudflare Durable Objects.
- [Reaktor Graph Navigation, Layers and Live Views](https://reaktor.build/docs/reaktor-graph-hierarchical-ui) (2026-10-08, 31 min): Independent scope, semantic layers, detail and time: nested ports, stable boundary summaries, source/runtime selection, extraction and live scene behavior.
- [Reaktor Graph Protocol](https://reaktor.build/docs/reaktor-graph-protocol) (2026-10-08, 27 min): The rgp/1 wire protocol: one connection over many targets with a session each, six independently-enabled domains (Mesh, Graph, Wire, Revision, Edit, Value) with typed commands, events and payloads, handle-based lazy resolution so a twenty-thousand-node graph is tractable, Kubernetes-style list-then-watch cursors where a gap is an error rather than silence, producer-side selectors, credited streams that drop rather than block the runtime being inspected, a patch-based write path that must declare document/source/runtime, and a derived revision digest that makes one system running several deployed revisions present honestly as several graphs. Includes a comparison against Chrome DevTools Protocol, LSP, DAP, the Kubernetes watch API, Erlang tracing and OpenTelemetry: what is borrowed, and what is refused.
- [Reaktor Graph Sources - bring existing systems into the graph](https://reaktor.build/docs/reaktor-graph-sources) (2026-10-08, 13 min): Show existing Python, Go, Spring, JS, and other services in the Reaktor graph without pretending Reaktor fully owns them. Each node says how it was learned, how trusted it is, and how fresh it is; those facts decide whether the desktop can only inspect it, open source, wrap it, or safely mutate it.
- [Reaktor Graph — Data-oriented Substrate and Typed Maps](https://reaktor.build/docs/reaktor-graph-substrate-redesign) (2026-10-08, 86 min): Proposed port-graph evolution: pure data, typed maps, owned runtimes, portable Kotlin logic and integration contracts for all 34 framework module/build directories, 13 desktop modes and 74 authored subpanes.
- [Reaktor Living Graph — System Architecture](https://reaktor.build/docs/reaktor-unified-system-graph) (2026-10-08, 43 min): One heterogeneous, nested, multilayer port graph across source, build and runtime: contracts, visitors, computation profiles, graph changes, cloud, evidence and AI.
- [Reaktor Component Lifecycle](https://reaktor.build/docs/reaktor-component-lifecycle) (2026-10-07, 15 min): Simple lifecycle contract across Android, iOS, browser, Worker, server, and graph-native attach, detach, activation, and port wiring events.

### Correctness and foundations

- [Reaktor Formal Methods — a correctness-carrying platform for agents](https://reaktor.build/docs/reaktor-formal-methods) (2026-10-08, 56 min): How Reaktor makes applications inherit machine-checked guarantees: the graph as executable and specification IR, a semantic boundary where effects happen only through modeled primitives with one labeled unsafe door, module-contributed invariants as data, GraphPatch as a formal transition system, a verification portfolio from deterministic checks through SMT, Alloy, TLA+/Quint and Lean, counterexamples returned to coding agents as structured findings, model-based and trace-conformance testing, and a machine-readable assurance manifest.
- [Reaktor Stable Foundations — 5.6 Ultra](https://reaktor.build/docs/reaktor-stable-foundations-5.6-ultra) (2026-10-08, 72 min): Code-grounded stable-kernel architecture for canonical graph semantics, transactional mutation, owned runtimes, authority, persistence, actors, protocols, FFI, and honest formal-verification claims.
- [Reaktor Verified Foundations — Fable 5](https://reaktor.build/docs/reaktor-verified-foundations-fable-5) (2026-10-08, 46 min): Claude's independent code-grounded foundation audit: numbered defects, invariant catalogue, verification ladder, distributed-plane security gates, and the primitive gaps that most increase Reaktor's power.

### Migration plans

- [Reaktor Graph Refinement Plan](https://reaktor.build/docs/reaktor-graph-refinement-plan) (2026-10-08, 19 min): Stronger types, port shapes, hook controllers, behavior actors, route tables, and module supervision.

## Build and ship

The toolchain, deployment and fleet resources that take a working change into production. Operations & Reliability owns diagnostics and verification.

### Toolchain

- [Reaktor Build Tools](https://reaktor.build/docs/reaktor-build-tools) (2026-10-08, 16 min): The plain-language map for the current Reaktor and BestBuds build toolchain: what Dependeasy owns, what Reaktor CLI reads today, where build/deploy work is duplicated, and which adapters should be added next.
- [Reaktor CLI — one command line for every reaktor app](https://reaktor.build/docs/reaktor-cli) (2026-10-08, 24 min): The terminal face of the Reaktor task catalog: a Kotlin CLI that discovers targets, Gradle modules, npm scripts, tool families, logs, deploys, tests, and doctor checks from the current project.
- [Reaktor DevOps — build, deploy, and operate the graph](https://reaktor.build/docs/reaktor-devops) (2026-10-08, 21 min): The build/deploy/operate plane: deployment and capacity as graph operations, one app partitioned across runtime targets and GCP/k3s cells, Dagger pipeline-as-code, Pulumi materializers, gated operations, Reaktor-managed capacity, customer-owned GCP cell attachment, and reaktorDesktop as the developer portal.
- [Dependeasy - Reaktor build control plane](https://reaktor.build/docs/reaktor-dependeasy) (2026-10-07, 16 min): Dependeasy as Reaktor's Gradle/KMP build fact producer for Reaktor CLI, desktop, MCP, and CI: current plugin behavior, target manifests, native/JS/mobile coverage, and the next adapter work.

### Cloud and fleet

- [Reaktor Cloud Control Plane](https://reaktor.build/docs/reaktor-cloud-pane) (2026-10-08, 15 min): GCP-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.
- [Reaktor at Mega-Scale](https://reaktor.build/docs/reaktor-megascale-strategy) (2026-10-08, 15 min): How Reaktor should scale into large engineering orgs: local-first runtime islands, graph-visible deployment cuts, typed service contracts, production backend discipline, and actors/Durable Objects as one stateful partitioning lane rather than the center of the story.

### Running in production

- [Reaktor Secrets](https://reaktor.build/docs/secrets-management) (2026-10-08, 8 min): Implemented reaktor-secrets seed for GCP Secret Manager, Cloudflare bindings, and BestBuds JVM credentials, plus the cache-first materialization plan.
- [Security Implementation Plan](https://reaktor.build/docs/security-plan) (2026-10-08, 6 min): Threat model and hardening plan for services, workbench operations, and mutating commands.

## Operations & Reliability

Shared observability, instance health, profiling, realistic load and the Shadow textbook: evidence from graph and source to a repeatable experiment.

### Start and source map

- [Operations & Reliability](https://reaktor.build/docs/operations) (2026-10-08, 5 min): Shared observability, graph evidence, instance diagnostics and the complete Shadow textbook reading map.
- [Operations Sources and Document Register](https://reaktor.build/docs/operations-references) (2026-10-08, 9 min): Every Shadow textbook chapter mapped to a page, related Reaktor documents reconciled and implementation/source evidence indexed.

### Observability and graph evidence

- [Native diagnostics with Crashlytics](https://reaktor.build/docs/operations-crashlytics) (2026-10-08, 9 min): Crashlytics release qualification, Reaktor session and trace correlation, explicit breadcrumbs, Firebase Performance, kernel reads, privacy and bounded client evidence.
- [Graph Attribution and Operational Evidence](https://reaktor.build/docs/operations-graph-evidence) (2026-10-08, 4 min): Exact source, graph, artifact and activation identity across telemetry, profiles, instance metrics and Shadow experiments.
- [Shared Observability and Shadow Evidence](https://reaktor.build/docs/operations-observability) (2026-10-08, 5 min): Retained Grafana/ClickHouse roles, proposed WAE hot comparisons and R2/Iceberg evidence, with delivery and retention contracts.
- [Performance and Observability](https://reaktor.build/docs/performance-observability) (2026-10-08, 6 min): Current-source operating overview for shared telemetry, instance diagnosis, profiling, controlled workloads and measurement gates.
- [Reaktor Analytics and Telemetry](https://reaktor.build/docs/reaktor-analytics-telemetry) (2026-10-08, 25 min): Product event catalogs and OTel graph conventions, reconciled with existing ClickHouse/Crashlytics and proposed Shadow hot/archive evidence.

### Instance health, profiling and load

- [Instance Health, Footprint and Memory Leaks](https://reaktor.build/docs/operations-instance-diagnostics) (2026-10-08, 5 min): App size, process/thread counts, CPU, managed/native memory, GC, resource pressure and repeatable leak diagnosis.
- [Load, Capacity and Resilience Verification](https://reaktor.build/docs/operations-load-resilience) (2026-10-08, 4 min): Textbook chapter 13: real dependencies, representative arrival models, capacity, soak/leak tests, faults and AI evaluation boundaries.
- [Profiling and JVM Diagnosis](https://reaktor.build/docs/operations-profiling) (2026-10-08, 4 min): Practical JVM JFR, thread, NMT and sampled-profile workflows, cross-platform capture qualification and retained evidence.
- [Reaktor DevTools](https://reaktor.build/docs/reaktor-devtools) (2026-10-08, 25 min): The workbench pane that mirrors real Android and iOS phones side by side and shows what the app is doing: the UI tree from each phone with parity and accessibility checks, network capture with a query language, HAR export, network conditions and blocking, logs, a timeline whose filmstrip replays the screen, Lighthouse-style audits scored on Lighthouse's curve against Android vitals and Apple thresholds, graph port stats and device controls. Compared with Chrome DevTools, Lighthouse, Android Studio, Xcode, VS Code, Flutter and React Native DevTools, Unreal's tools and measure.sh.
- [Reaktor Tooling Layer](https://reaktor.build/docs/reaktor-tooling-layer) (2026-10-08, 22 min): How reaktor-tooling connects adb, simctl, idb, HTTP proxies and debuggers to the graph protocol without becoming a plugin set: three nouns (probe, adapter, attachment), an attachment that is literally an rgp target so a device-hosted app is addressed exactly as a Worker is, and a six-rung fidelity ladder (discovered, enumerated, sampled, streamed, attributed, interactive) whose rung is a property of a fact rather than of a target — so one device can serve a live graph read, a log stream and a one-shot view dump at once without any of them borrowing the others' credibility. Specifies per-platform transports, the correlation header that joins proxy-observed bytes to graph ports, the constraints on CA install and debugger attach, and the collapse of device commands and graph patches onto one prepare/execute path with one ledger.

### Reaktor Shadow textbook

- [Shadow Backends and Keploy Qualification](https://reaktor.build/docs/shadow-backends) (2026-10-08, 4 min): Textbook chapters 10–11: current Keploy adapter limits and version-qualified local, preview and deployed backend choices.
- [Shadow Capture Fabric](https://reaktor.build/docs/shadow-capture-fabric) (2026-10-08, 8 min): Capture all supported graph, JVM, eBPF/kernel, JavaScript, Worker, Kubernetes, state and client evidence with explicit coverage and replay capability.
- [Shadow Capture, Replay and Fidelity](https://reaktor.build/docs/shadow-capture-replay) (2026-10-08, 4 min): Textbook chapters 7–9: graph-selected operation journals, ES6 facade sketch, async ordering, matching and fidelity coverage.
- [Shadow Clients, Live Updates and Agent Verification](https://reaktor.build/docs/shadow-clients-agents) (2026-10-08, 3 min): Textbook chapter 15: complete client journeys, Surface ownership, mixed revisions, live updates and fixed agent acceptance.
- [Reaktor Shadow — Moving Development and Verification](https://reaktor.build/docs/shadow-dev-environment) (2026-10-08, 8 min): The Shadow textbook entry point: moving sanitized bases, isolated pinned experiments, graph capture and paired verification.
- [Shadow Foundations — Moving State and Controlled Experiments](https://reaktor.build/docs/shadow-foundations) (2026-10-08, 3 min): Textbook chapters 1–3: moving production counterpart, equivalent pre-state, admitted workloads and explicit effect cuts.
- [Shadow Assertions, Privacy and Failure Capsules](https://reaktor.build/docs/shadow-verification) (2026-10-08, 3 min): Textbook chapters 12 and 14: fixed assertions, privacy, send/retry/reconnect, anomaly minimization and reproducible capsules.
- [Shadow Workspaces, Base Publication and Resource Isolation](https://reaktor.build/docs/shadow-workspaces) (2026-10-08, 4 min): Textbook chapters 4–6: plans/manifests, snapshot/CDC publication, leases and truthful isolation per resource.

### Integration and delivery

- [Operations Delivery Gates and Runbooks](https://reaktor.build/docs/operations-delivery) (2026-10-08, 5 min): Textbook chapter 16 and current-source delivery gates: safe moving dev, one real replay, evidence transport and operating health.
- [Reaktor Instrumentation Plan](https://reaktor.build/docs/reaktor-instrumentation-plan) (2026-10-08, 26 min): October source reconciliation and current delivery gates, retaining the September numbered instrumentation register as dated design.
- [Reaktor Workbench Links](https://reaktor.build/docs/reaktor-workbench-links) (2026-10-08, 5 min): How Reaktor Desktop's panes connect: a screen in the running app to its service, the Cloudflare worker that serves it through the gateway, the databases it touches and the Data targets for them, and back from any store to the workers, services and screens that depend on it. What Graph, Cloud, Data, DevTools, Deploy and Analytics each show from the others, live product analytics from ClickHouse, the system_trace MCP read, and the limits of the link rules.

## Workbench

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.

- [Hangar — the Reaktor desktop app](https://reaktor.build/docs/hangar) (2026-10-08, 8 min): What Hangar is and how its window works: one title row, the macOS menu bar the way IntelliJ uses it, the twelve panes with their shortcuts and docs, how panes link, and the one map style every graph shares.
- [Reaktor Arena](https://reaktor.build/docs/reaktor-arena) (2026-10-08, 17 min): Unreal Engine simulation lab for validating Reaktor ideas through combat, AI, algorithms, traces, scenario replay, and future graph orchestration.
- [Reaktor Product Atlas — Living Graph Super-IDE](https://reaktor.build/docs/reaktor-atlas-revamp-5.6-ultra) (2026-10-08, 119 min): The 122-board software engine atlas: 61 current workspace handoffs, including 18 Living Graph workspaces, whole-system graphs, composable modules, persistent editors, Conductor harnesses, cloud placement, devices, delivery, telemetry, analytics and retained specialist references.
- [Reaktor Cloud](https://reaktor.build/docs/reaktor-cloud) (2026-10-08, 18 min): The workbench pane that reads Cloudflare, Google Cloud and the Kubernetes cluster through the control plane, joins them with what the repository declares, and shows one graph from hostname to machine: a map drawn by the Graph pane's renderer, one frame per service packed to the window's shape, with neighbourhoods and paths, provider tabs, findings with evidence, drift, a change timeline, cost quantities and MCP reads for agents; and every operation of the Cloudflare, Supabase and Google Cloud APIs, read from the providers' own descriptions and callable from Hangar and the agent door, with changes behind approval. Compared with Headlamp, App Hub, CloudWatch Application Signals, Wiz, Komodor, CloudQuery and OpenCost.
- [Reaktor Desktop Master Plan](https://reaktor.build/docs/reaktor-desktop-master-plan) (2026-10-08, 190 min): The 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 document.
- [Reaktor Graph](https://reaktor.build/docs/reaktor-graph-pane) (2026-10-08, 17 min): The workbench pane that shows a running app's graph in the visual language of Unreal Blueprints: every feature as a frame packed to the window's shape, nodes with coloured headers, pins coloured by what flows through them, dashed links for the routes between screens, calls pulsing along wires, watched pin values from a phone, an execution trace, a summary card and an outline of the whole system. Reads this desktop or a phone over the DevTools agent; ELK layout; findings for unwired, duplicate, cyclic, layered and unreachable wiring; a ports table and MCP reads. Compared with Unreal Blueprints, Nx, IntelliJ, dependency-cruiser, SonarQube, Kiali, NiFi and Stately.
- [Reaktor UI/UX Audit — 8 September 2026](https://reaktor.build/docs/reaktor-ui-ux-audit-2026-09-08) (2026-10-08, 142 min): Living 122-board audit with native narrow/ultrawide evidence: repairs as they land, remaining visual and interaction issues, domain integration gaps and measurable acceptance journeys.
- [Reaktor Visual Language (Blueprints)](https://reaktor.build/docs/reaktor-visual-language) (2026-10-08, 38 min): A Blueprints-style visual language on reaktor-graph: author app behavior, workflows, and whole-system orchestration, with agents as first-class co-authors.
- [Reaktor Workbench Layers — Tooling, Kernel and Hosts](https://reaktor.build/docs/reaktor-workbench-layers) (2026-10-08, 27 min): The implemented boundaries between reusable tooling, headless graph runtime, the workspace kernel, CLI, desktop and MCP; service ownership, operation receipts, connection evidence and credentials.

## Agents

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.

### Building Reaktor with agents

- [Building Reaktor with agents — where the tokens go, and how to spend fewer](https://reaktor.build/docs/reaktor-agent-efficiency) (2026-10-08, 13 min): A field report from one large multi-agent session: where about 19 million tokens went, the MCP reads, guards and headless flows agents should use today, and ten ordered enhancements — codemods, one verify call with typed results, context packs, design-bar guards, a hermetic test kit, per-agent workspaces with a merge queue, scaffolds, structured output, stable ids and build hygiene.

### Agents calling Reaktor

- [The Reaktor Control Plane](https://reaktor.build/docs/reaktor-agentic-tooling) (2026-10-08, 18 min): MCP, Koog, graph snapshots, typed tools, permission-gated mutations, and command queues.

### Reaktor driving agents

- [Reaktor Conductor — driving Claude Code and Codex from inside Reaktor](https://reaktor.build/docs/reaktor-conductor) (2026-10-08, 34 min): The outbound agent layer: user-defined agents, one canonical Reaktor-owned conversation stored as a causal event DAG, per-agent context packets with explicit visibility rules and documented isolation limits, protocols the operator writes as data, and Claude Code and Codex driven as ordinary supervised subprocesses so each harness keeps its own tools and configuration. Then the design half: what a turn costs, and what Reaktor would have to compile, reduce, check and measure so that a frontier model is paid only for the part of a turn it is the only thing capable of doing.
- [Reaktor Agent Workspace — Native Harnesses, Graph Context and Verified Work](https://reaktor.build/docs/reaktor-agent-workspace) (2026-10-08, 53 min): Graph-first native Codex and Claude integration through an extension bundle and desktop session adapters: effort controls, typed findings, local context, evidence, orchestration and the workspace UI, with implemented behavior separated from proposals.

### Agents in products and tools

- [Koog in reaktorDesktop](https://reaktor.build/docs/reaktor-koog-workbench) (2026-10-08, 16 min): Replace fixture agents with Koog-backed structured workbench commands and Critic review.
- [Koog for the BestBuds Bot](https://reaktor.build/docs/reaktor-koog-agents) (2026-10-08, 14 min): JVM Koog brain for bot and moderation, with Cloudflare edge pre-filtering.
- [Browser-Local AI for Reaktor](https://reaktor.build/docs/reaktor-browser-local-ai) (2026-10-08, 15 min): How Chrome built-in Gemini Nano APIs and WebLLM provide local AI capabilities for docs, graph explanations, workbench suggestions, and draft graph operations.
- [Gemini DevOps Agent](https://reaktor.build/docs/reaktor-gemini-devops-agent) (2026-10-08, 10 min): Bounded Antigravity CLI handoff layer for delegating BestBuds/Reaktor build, test, deploy, log, replay, and live-ops execution to Gemini 3.5 Flash High.

## Products built on Reaktor

Real applications on the framework. They are the honesty check: anything the framework claims has to survive one of these.

- [Nexergy on Reaktor — Commerce Substrate Design](https://reaktor.build/docs/claude-nexergy-appweb-analysis) (2026-10-08, 18 min): Production design for Nexergy Energy — a real B2B biomass trader-aggregator startup — built entirely on Reaktor primitives and wiring, grounded in how B2B commerce actually operates (OfBusiness, Buyofuel, BiofuelCircle, Udaan; composable-commerce/MACH capability maps; the canonical capture→…→analyse OMS flow). Maps the full commerce capability surface onto existing modules plus a minimal new substrate — reaktor-ledger (keystone), reaktor-catalog, reaktor-fulfillment, plus thin audit-journal and compliance-gate primitives, all factored as general primitives (no reaktor-biomass vertical) — and makes embedded working-capital credit the trader-aggregator moat. OMS/WMS/TMS/returns/financing are composition recipes; Nexergy Energy is the startup platform.
- [Codex Nexergy Energy on Reaktor](https://reaktor.build/docs/codex-nexergy-appweb-analysis) (2026-10-08, 24 min): Market-scanned target architecture and high-level subsystem map for Nexergy Energy, the production B2B biomass trader-aggregator platform running on feature-complete Reaktor: commerce, inventory/WMS, logistics/LMS, ledger/audit, graph workflow, credit, and service primitives without a biomass-specific module.
- [CompanyOS — TypeScript / Vite / Reaktor Migration Plan](https://reaktor.build/docs/companyos-migration-plan) (2026-10-08, 29 min): CompanyOS migration record covering the landed TypeScript/Vite cutover, typed service contract, Browser Run portal sessions, Cloudflare Workflow DAG runner, Playwright gates, and 20 routine automation recipes.
- [Manna — Functional Design Handoff](https://reaktor.build/docs/manna-functional-designs) (2026-10-08, 13 min): The expanded Manna Pencil specification: 42 desktop and 43 mobile screens, the full multilayer Atlas, connected workflows, editing and recovery states.
- [Manna HLD — Implementation on Reaktor Graph and Surface](https://reaktor.build/docs/manna-hld) (2026-10-08, 46 min): Manna's mobile and desktop web architecture: scoped Reaktor graphs, typed ports and actors, Surface behavior, a full multilayer knowledge map, data ownership, AI, offline recovery and legacy migration.
- [Manna — Kotlin Surface migration plan](https://reaktor.build/docs/manna-kotlin-surface-migration-plan) (2026-10-08, 27 min): One shared Kotlin Surface application, Kotlin React web and Compose native realizations, adaptive layouts, typed editor islands and retirement of handwritten Manna TypeScript/CSS.

## Background and archive

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.

### Market and critique

- [Claude Critic Review](https://reaktor.build/docs/claude-critic-review) (2026-10-08, 15 min): Adversarial review of architecture, feasibility, competition, and go-to-market risk.
- [Codex Critic Review](https://reaktor.build/docs/codex-critic-review) (2026-10-08, 13 min): Skeptical counterarguments against the full Reaktor control-plane vision.
- [Competitive Landscape](https://reaktor.build/docs/reaktor-competitive-analysis) (2026-10-08, 12 min): Durable positioning map for Reaktor against app generators, visual builders, workflow canvases, statechart tools, Blueprints, and AI coding agents, with shipped-vs-designed status called out.

### Earlier roadmaps

- [Codex Roadmap](https://reaktor.build/docs/codex-roadmap) (2026-10-08, 20 min): Code-grounded roadmap for turning the workbench prototype into a real control plane.
- [Implementation Plan](https://reaktor.build/docs/reaktor-implementation-plan) (2026-10-08, 18 min): Execution plan for moving from prototype to production workbench and Compose/web targets.
- [Strategic Roadmap](https://reaktor.build/docs/reaktor-workbench-roadmap) (2026-10-08, 19 min): Product and platform roadmap: phases, modules, moats, risks, and success metrics.

### Prior research and reports

- [Claude Dev Environment](https://reaktor.build/docs/claude-dev-environment) (2026-10-08, 28 min): Original shadow/dev-environment draft preserved for design lineage.
- [Codex Dev Environment](https://reaktor.build/docs/codex-dev-environment) (2026-10-08, 12 min): Original capsule taxonomy, environment classes, materialisation workflow, and response comparison draft.
- [Engine and Website Implementation Report](https://reaktor.build/docs/engine-website-implementation-report) (2026-10-08, 10 min): KMM engine migration, Kotlin/React website renderer, Compose parity, tests, and graph pain points.
- [Flow Analysis](https://reaktor.build/docs/flow-analysis) (2026-10-08, 9 min): react-flow, compose-flow, and reaktor-flow comparison for visual graph editing.
- [Performance design history](https://reaktor.build/docs/performance-observability-history) (2026-10-08, 40 min): Superseded performance/observability design and September reviews preserved before the October reconciliation.
- [Workbench Feature Gap Analysis](https://reaktor.build/docs/reaktor-architecture-analysis) (2026-10-08, 8 min): Prototype screen gaps, differentiators, implementation priorities, and inspector coverage.
- [Reaktor Product Atlas — Original Source Review — Fable 5](https://reaktor.build/docs/reaktor-atlas-review-fable-5) (2026-10-08, 464 min): Claude's original exhaustive board inventory, measurements, contradiction audit, and pane-by-pane reasoning, retained publicly as auditable source material for the canonical combined atlas.
- [Reaktor Desktop v3](https://reaktor.build/docs/reaktor-desktop-v3) (2026-10-08, 1 min): Interactive high-fidelity desktop workbench artifact.
- [Reaktor Graph Migration Plan](https://reaktor.build/docs/reaktor-graph-migration-plan) (2026-10-08, 18 min): Tighten RouteBinding, navigation edges, themed UI scope, and graph runtime ergonomics.
- [Shadow design history](https://reaktor.build/docs/shadow-design-history) (2026-10-08, 63 min): Superseded merged Shadow design preserved for lineage; current semantics are defined by the textbook pages.