Find a starting point

Start with what matters to you.

Choose a subject that interests you. Start with the project’s plain-language example, then explore an article or a development note.

A reading path

Control & Simulation

Follow a simulated drone from sensor outages to measured recovery and the failures that remain after a landing mitigation.

  1. System

    AeroLoop

    A simulation-only drone laboratory measuring sensor-outage recovery and capture-aware landing. The retained stress studies report accepted: false, with replayable flight evidence and explicit failure boundaries.

  2. Article

    How Long Can a Drone Controller Fly Blind? Measuring Recovery From Sensor Outages

    AeroLoop's retained simulation study recovers from 500 ms missing captures under the tested conditions. One- and two-second gaps expose a failure boundary that prediction and a landing guard do not close.

  3. Engineering note

    AeroLoop finds the edge of its sensor-outage envelope

    500 ms profiles recover in the retained baseline study. One-second cases are mixed and all two-second missions fail. Later prediction and landing-guard studies still report accepted: false.

A reading path

I build embedded systems

See how a Linux program talks to a simulated device, from sending a request to receiving a result.

  1. System

    Yocto + QEMU EDU Lab

    A hands-on lab for building Linux images and learning how drivers communicate with simulated devices on two processor architectures.

  2. Article

    PCI Driver vs Platform Driver: What Changes Between x86-64 and ARM64?

    Compare two explicit virtual-device contracts across discovery, MMIO, interrupts and evidence without confusing CPU architecture with bus type.

  3. Engineering note

    Independent PCI and ARM64 learning paths

    Closed lab manifests now separate x86-64 PCI MSI/INTx and bounded DMA from an ARM64 Device Tree and platform-driver path. The ARM64 peripheral has its own hardware contract and does not expose DMA.

A reading path

I work on AI and agents

See how an AI tool can change a 3D scene and check what it sees.

  1. System

    Cogniform

    A 3D engine that lets software and AI tools change a scene, then inspect images and object data from the same scene version.

  2. Article

    An Observation Needs a World Revision

    What Cogniform's revision-linked observations clarify about agent feedback, local transport and evidence.

  3. Engineering note

    Bounded local agent sessions

    The CLI now documents inherited-stream sessions and a local MCP adapter for queries, imagination, atomic patches, and revision-linked observations. These adapters add no network listener or remote security boundary.

A reading path

I want to understand replay

Learn how recording inputs lets you repeat a game session and check the result.

  1. System

    LudoWeave Engine

    A Python engine for small 2D worlds with verified replay, pause and single-step controls, seek/resume, and a tick-aware playback status panel.

  2. Article

    A Replay Is More Than a List of Inputs

    How consumed input snapshots, world transactions and independent verification make a recording useful evidence.

  3. Engineering note

    Record play sessions, verify them headlessly

    Clockwork Arena can record the input snapshots its play loop consumes and verify them in a fresh headless process. Recording is opt-in, capped at 3,600 requested ticks, and keeps rendering and audio outside the artifact.

A reading path

I want to understand operating systems

Follow a small system from startup to running programs with limited permissions.

  1. System

    MakopaOS

    A small operating system lab for studying how a computer boots, runs isolated programs and controls access to resources.

  2. Article

    Where AI Fits in the Larger System

    What recent work on agent standards, on-device inference, and reliability has reinforced for me about building AI into real products.

  3. Engineering note

    From boot sector to explicit kernel authority

    The retained BIOS example is now accompanied by a freestanding Rust kernel and thin UEFI loader. Fixed workloads exercise task isolation, capability-mediated IPC, a bounded approval broker, and a supervisor-readable effect journal.