0x1d1e
INDEPENDENT SOFTWARE EXPERIMENTS01 / IDLE CYCLES

0x1d1e

software made
during idle cycles.

A loose group of people building software in the time between everything else.

Infrastructure. Agents. Interfaces.
Whatever seems interesting next.

Explore the experiments
SPARE TIME → WORKING SOFTWARESCROLL TO THE WORKBENCH
02 / THE WORKBENCHA FEW DIRECTIONS. NO FIXED DESTINATION.

Loose interests.
Working
connections.

Small experiments in software and systems. Built whenever there are spare cycles.

SELECT A DIRECTION → FIND AN EXPERIMENT
AN EXPERIMENT, IN FIVE VERBS
  1. Be curious
  2. Build
  3. Run
  4. Verify
  5. Keep or discard

An organizing idea. Not an internal pipeline.

03 / SELECTED EXPERIMENTSPUBLIC CODE. OPEN QUESTIONS.

Less hypothetical.
More hands-on.

Three things we built.
Three different ways to try an idea.

EXPERIMENT / 01

Kanade

A top-center Dynamic Island for the niri Wayland compositor.

RUST / AMANE / NIRI
01 / INTERFACE STUDYniri · Wayland
23:48
ONE ANCHOR. DIFFERENT FORMS.

At rest, the island shows the clock.

Illustrative reconstruction. State buttons stand in for desktop events, hover and click.

EXPERIMENTAL / CHECK THE REPOSITORY
EXPERIMENT / 02

Kinetix

A self-hosted LLM gateway with executable Routes and fallback.

RUST / SELF-HOSTED / WASM PLUGINS
02 / ROUTING STUDYPriority + fallback
REQUESTClientCompatible API
VIRTUAL KEY → ROUTEKinetixOperator-defined priority
TARGET A / PRIMARYEligibleConfigured provider
TARGET B / FALLBACKEligibleConfigured provider
READY / ILLUSTRATIVE

Choose a scenario, then route a single illustrative request.

Conceptual Route. A and B are fictional operator-configured targets. No traffic or provider measurements.

EXPERIMENTAL / CHECK THE REPOSITORY

Version reboot planned. Kinetix and its plugins document breaking contract changes. Read the plan ↗

EXPERIMENT / 03

Merro

A Pi + tmux + Git project lead with independent review.

PI / TMUX / GIT
03 / LIFECYCLE STUDYPi + tmux + Git
LOCAL OBJECTIVE

Add keyboard navigation.

ONE CHANGESET / NO GITHUB REQUIRED
  1. 01

    Objective / Main

    Objective
  2. 02

    Implementer

    Waiting
  3. 03

    Independent reviewer

    Waiting
  4. 04

    Result / delivery

    Waiting
You → Main

Add keyboard navigation to a local interface.

Illustrative local-delivery path. No agents run here. Rejection starts a fresh implementer, then a fresh reviewer.

EXPERIMENTAL / CHECK THE REPOSITORY
04 / REPOSITORY INDEXTHE EXPERIMENTS & THEIR SATELLITES

There’s more
on the bench.

Primary projects, prototypes and the tools around them. Public code is not a stability guarantee.

7 REPOSITORIES / ALL

A selected public index, not a complete inventory. All repositories on GitHub ↗

05 / WHY WE BUILDFROM THE ORGANIZATION PROFILE ↗

What if
we just
built it?

Sometimes a useful tool.
Sometimes an answer to one question.
Both are valid outcomes.

  1. 01

    Build first

    Working software teaches more than discussing hypothetical software.

  2. 02

    Verify things

    Source code, measurements and reproductions beat guesses.

  3. 03

    Keep the useful parts

    An experiment can answer one question and stop there. That counts.

  4. 04

    No fake stability

    Public does not mean production-ready. Check the repository.

  5. 05

    No roadmap theater

    Projects move when someone wants to work on them. Intent is not a delivery date.

06 / OPEN ENDKEEP THE USEFUL PARTS.

Read the code.
Break it.
Keep the useful parts.

Explore GitHub Browse projects Contributing guidelines