Reading
Kortecx-core is a distributed runtime for AI Agents written in Rust, focusing on solving the exactly-once orchestration problem in Agent workflows and providing reliable fault recovery mechanisms for non-deterministic Agent steps that change the external world.
Section 01
Kortecx-core is a distributed runtime for AI Agents written in Rust, focusing on solving the exactly-once orchestration problem in Agent workflows and providing reliable fault recovery mechanisms for non-deterministic Agent steps that change the external world.
Section 02
Section 03
Most current Agent frameworks have fundamental flaws in handling fault recovery. Agent workflows differ from traditional data pipelines: Agent steps call model sampling and may change the external world—invoking tools, accessing APIs, writing to external systems. These operations cannot be safely recomputed: if a worker node crashes during execution, it may lead to duplicate payments, duplicate emails, or data with silent errors.
Existing frameworks usually use simple retry mechanisms or do not handle this at all, leading to hidden state leaking into worker node memory, fragile coordination via message queues, and no persistent records of attempts or successes. When problems occur, developers can only debug by reading logs.
Kortecx-core takes the opposite stance: every Agent attempt is a persistent fact appended to the log. During recovery, committed steps are never re-run—instead, results are re-read.
Section 04
Kortecx-core treats Agent workflows as a set of atomic operations requiring exactly-once semantics. This is similar to data stream processing systems like Spark, but with fundamental adjustments for Agent scenarios:
Section 05
Mote is the minimal indivisible unit for runtime scheduling, movement, and recovery. It is a persisted record of an attempt to do something, not a recomputable description. A committed Mote is a fact in the log and is never re-run during recovery.
Each Mote carries a non-deterministic label:
The runtime uses different recovery strategies based on the label: proactive recovery for safe labels, and operator-gated recovery for dangerous labels.
Section 06
The log is append-only, and the runtime's dependency graph is a projection folded from the log (event sourcing), never stored as a mutable graph. This makes the jump from single-node to distributed a matter of wiring, not rewriting.
Section 07
The log only carries a 32-byte content hash (ContentRef); the actual payload is stored in content storage using content-addressable naming. Automatic deduplication is a free side effect. The local file system implementation is open-sourced with the core, and S3 and replication implementations follow the same trait.
Section 08
Keep going with more reads from the same topic.
Nornir MCP Server is an enterprise-level server based on the Model Context Protocol (MCP). It seamlessly integrates large language models (such as Claude) with the Nornir network automation framework, supporting natural language orchestration for multi-vendor network devices (Cisco, Arista, Juniper, etc.), and providing production-grade features like a dual-engine architecture (NAPALM + Netmiko), intelligent filtering, and a secure sandbox.
Bibliothèque Française LLM is a structured indexing and annotation project for French public domain literature designed specifically for large language models (LLMs). It integrates multiple authoritative sources such as DraCor, Common Corpus, and Wikisource, providing metadata indexing categorized by genre, author, and era, as well as in-depth annotations for dramatic texts (including characters, lines, stage directions, etc.). Its aim is to enable LLMs to efficiently read and understand classic French literary works.
Splinter is a minimalist, high-performance key-value (KV) and vector storage system enabling zero-latency inter-process communication via shared memory and atomic operations. With only 766 lines of core code, it supports millions of operations per second and 768-dimensional vector storage, offering a new architectural approach for local LLM inference and data-intensive applications.
Folkering OS is the world's first AI-native bare-metal operating system, entirely written in Rust no_std without relying on Linux, POSIX, or libc. It can generate commands from scratch, compile them into WASM, and run them in 10 seconds, achieving true self-evolution.