Skip to content
RecursiveIntellINDEPENDENT SYSTEMS ENGINEERING

JOSH STEVENSON / INDEPENDENT ENGINEER

AI systems.
Built to be
understood.

Agents that act. Memory that persists. Infrastructure you can inspect. I build the systems underneath useful AI.

Explore the work ↗Meet the engineer →
RUST / PYTHON / TYPESCRIPTALBERTVILLE, AL · REMOTE U.S.SCROLL TO EXPLORE ↓

I work where agent behavior, persistent memory, and real software meet.

Independent applied R&D.
Public source. Explicit scope.

01 / SELECTED ENGINEERING

Ideas, carried
into code.

A focused path through the work. Start with a concrete runtime change, then explore the memory and infrastructure behind it.

01/03
Merged downstream runtime / source-validated

Ares + Recursive Agent unified runtime

Tool-using agents need context, authority, physical admission, provider egress, outcomes, and rollback to stay bound across the real execution path.

THE WORK

Ares now materializes governed context and staged releases while Recursive Agent owns managed physical admission, cumulative budgets, cancellation fencing, provider-egress binding, and receipt-bearing native execution.

Evidence & current scope +

Ares PRs #31 and #32 and recursive-agent PR #5 are merged. Reported checks include 126 focused Ares integration passes, 138 Ares runtime/distribution passes plus an isolated managed setup, and passing recursive-agent cargo check, test, fmt, and clippy gates.

This is the current RecursiveIntell Hermes integration path and merged source state. It does not establish live-provider behavior, production readiness, or completed post-merge activation across gateway, Desktop, and MCP surfaces.

Read the unified runtime case↗
02/03
Current core / R&D system

Mnemes and semantic-memory

Agent memory must persist, retrieve relevant prior state, preserve provenance and time, and remain operator-owned.

THE WORK

A Rust-first memory engine, MCP access layer, agent integration kits, and self-hosted Mnemes server with explicit ownership boundaries.

Evidence & current scope +

Public repositories, crates, documentation, tests, and a dedicated product/proof surface.

Public artifacts establish implementation scope, not customer adoption, universal correctness, or production fitness.

Inspect semantic-memory↗
03/03
Recovery / installer prototype

Recursive Linux recovery workbench

A workstation supporting long-running AI work needs a recoverable operating environment without silently taking storage, credential, or device authority.

THE WORK

A Fedora 44 recovery-oriented workstation installer prototype packages bounded Wi-Fi recovery, targeted PCIe ASPM mitigation, TLP policy, disk reporting, health projection, and Hermes Workbench profiles while leaving destructive storage and identity choices interactive.

Evidence & current scope +

Public source includes a structurally checked hardware-target ISO candidate, a disposable BIOS/QEMU install-and-boot fixture, project tests, and a sanitized evidence receipt dated September 6, 2026.

The repository remains NO-GO for physical USB writing or laptop installation. UEFI installed-system behavior, physical-media validity, full workstation restoration, and hardware safety remain unverified.

Inspect Recursive Linux↗
All selected work ↗Explore the repository library ↗

02 / THE MEMORY SYSTEM

Meet
Mnemes.

A personal, self-hosted agent memory server. Keep durable context, source history, and device ownership close to the system that uses them.

Explore Mnemes ↗

Public software and research. Hardware deployment and production fitness have their own evidence requirements.

01 / CAPTUREA conversation.Keep the source.
02 / RETAINA memory.Preserve the history.
03 / RETRIEVEUseful context.Return to the evidence.

03 / HOW I WORK

Make the difficult
parts visible.

The work is more useful when another engineer can understand the decision, reproduce the result, and see what still needs testing.

01

Start with the failure.

Trace the actual behavior before adding another layer. Name the owner of state, decisions, and effects.

02

Build a focused change.

Keep the useful boundary small enough to explain, test, review, and hand off.

03

Show what happened.

Link the source and the result. Keep test evidence, deployment evidence, and open questions distinct.

IN THE OPEN

Teknium, creator of Hermes Agent, highlighted my RecursiveIntell-enhanced Hermes demonstration.

View the original interaction ↗This is a public interaction around Josh’s engineering work, not a customer testimonial, partnership, or product endorsement.
THE NEXT CONVERSATION

Good systems start
with a clear question.

Hiring for agent infrastructure? Working through a difficult system? Tell me what you’re trying to make work.

Start a conversation ↗