← Preview Hub

CADE LABS · LIVING SYSTEM MAP

Everything connects.

A phone-first view of the products, repositories, harnesses, control systems and execution backends that make up Cade Labs.

08 Oct 2026 Built after a real Little Hearth mobile session outlived GitHub Actions and exposed the need for interchangeable runners.
Control Build & publish Verification Products Planned

PRODUCT PORTFOLIO

What the system is building

Repos, games, tools and preview-only experiments shown separately from the infrastructure that supports them.

THE REASON BEHIND THE ARCHITECTURE

A real constraint became a product direction.

  1. 01
    Build from the phone

    Little Hearth was being actively developed and playtested on Android with no laptop available.

  2. 02
    Fix the real device, not the synthetic test

    The M8 movement architecture replaced a fragile timer-driven route with an atomic mobile route after repeated one-tile failures on the real phone.

  3. 03
    The CI machine disappeared

    GitHub Actions jobs queued and then failed before executing a single step. The existing harness logic was still good, but local execution assumed a computer was switched on.

  4. 04
    Separate control from execution

    GitHub stays source of truth. The phone becomes the control plane. The runner can be browser simulation, Cloudflare browser, Codespaces, a Cade runner or GitHub Actions.

  5. 05
    The target

    From one web dashboard: choose repo + exact SHA → Quick Test → Visual Test → Full Test → evidence. No single provider gets to stop development.

CORE PRINCIPLE GitHub Actions is one execution backend. It is not the testing system.