About the lab behind NeuroChain DSL.

StellarZeroLab is the product surface around NeuroChain DSL: a lightweight, developer-first language and demo stack built to keep AI operations explicit, local when possible, and easy to reason about.

DSL AI and logic kept in one readable flow
Local-first CPU ONNX inference and smaller moving parts
Real demos WebUI and Stellar surfaces tied to live code paths
What matters here
  • Deterministic over magical The goal is not vague AI orchestration. The goal is explicit behavior that can be inspected, tested, and reviewed.
  • Integration over mockups The public pages are not just screenshots. They reflect the actual server, runtime, and product direction we are building.
  • Guardrails before automation Especially on the Stellar path, typed plans and safety checks come before any ambition to automate more.

What StellarZeroLab builds

The public surface is intentionally compact: one engine, one real server path, and demos that explain the design through use rather than marketing copy alone.

NeuroChain DSL

A language where AI-builtins sit directly in the script instead of being pushed into opaque wrappers and side systems.

WebUI

A browser surface for trying the DSL quickly, selecting models, viewing output, and testing the same runtime path exposed by the API.

Stellar Demo

A guarded testnet-first path for turning user intent into typed plans that can later deepen into contract-aware Soroban workflows.

How we think about the stack

The design bias is simple: keep the execution model understandable, keep the public demos honest, and keep the system small enough that behavior stays legible.

NeuroChain DSL exists because AI integration too often disappears into glue code, black-box orchestration, and UI layers that look impressive but reveal very little. The approach here is narrower and more deliberate: put AI operations into code, keep the runtime explicit, and make the public surfaces reflect the real architecture.

  • Local inference on CPU where it makes sense, instead of defaulting to hidden remote layers.
  • Typed plans and guardrails before any action path becomes deeper or more automatic.
  • One production repo and one public story, so technical reviewers can connect the dots quickly.

How this started

This did not begin as a polished product plan. It spent roughly a year taking shape through technical curiosity, iteration, and a growing interest in blockchain infrastructure, especially Stellar.

A year of shaping

The project developed gradually rather than all at once: first as a line of thought, then as experiments, and finally as a clearer system with one readable direction.

Stellar as a catalyst

Interest in blockchain technology, and especially Stellar, pushed the work toward typed plans, explicit guardrails, and flows that can be reasoned about before anything is submitted.

One-person core project

At its core, this is a one-person project. The public site, demos, and direction are being shaped and built by one person.

See the lab through the live surfaces

The clearest way to understand StellarZeroLab is still to open the public demos and follow the roadmap from there.