The engineering journal / 2026

Notes from
the workbench.

A PERSONAL RECORD, NOT A PRESS RELEASE

Some projects become products. Others start because a tool does almost everything I need, except the part that makes it work in my own setup.

Baishalya RoulBuilding in public, selectively ↗
01 / Featured writing

Inside the build

Architecture · integration · trade-offs
Deep dive / ModelBridge

The part between the model and the sandbox.

Why I built a routing and control layer for my local AI-agent workflow, how NVIDIA OpenShell fitted into the setup, and the limits I still have to account for.

PythonProvider routingOpenShell · third-party runtime
Read the engineering note ↗
02 / Shorter notes

Recent thinking

The reasoning behind the implementation
Rust / fresh architecture

Starting clean with Xonext

Separating the engine, runtime adapters, storage and interfaces before writing another oversized application. A fresh Rust direction, not a rebrand of the earlier work.

Read the note ↗Work in progress
OpenShell Engine / tooling

One interface is never the whole system.

Building CLI and browser-based control surfaces around runtime operations made me think harder about command parity, failure visibility and version-specific behavior.

Related field note ↗Independent tooling
Release engineering / practice

Tests are a checkpoint, not a headline.

A passing suite is useful, but the harder work is knowing which environment, dependency versions and live workflows the result actually covers.

03 / Beyond the product pages

Also on the bench.

Smaller experiments and systems work do not always need a release button. These are areas I've been exploring separately from my published applications.

01LAVIS

A desktop-assistant experiment in Python, with a focus on local execution and tool-oriented workflows.

02RecoverCore

File and storage recovery exploration: scanning, filtering and thinking through what can reasonably be recovered.

03n8n-mod

Workflow tooling and integration experiments. Research and repository activity should not be mistaken for a supported public release.

04OpenShell Engine

Independent management and automation tooling around third-party sandbox infrastructure, with version-specific compatibility considerations.

About third-party technology

These notes describe independent work with existing open-source systems. References to NVIDIA OpenShell identify an external technology, not a collaboration, certification or endorsement.

Read the attribution note ↗