Independent engineering lab for AI-native systems and production software.

marcellelabs.io

Design → Build → Evaluate → Ship.

We take a technical problem through architecture, implementation, evaluation, deployment and verification — and we publish the evidence for each stage rather than asserting the outcome. Every system below states what its evidence establishes and, explicitly, what it does not.

Problem. Two agent actions can each be locally valid and still break a shared constraint when they land together. Local validity does not compose.

System. Interlock reads revision-bound environment evidence before shared-state mutation and selects a deterministic coordination decision.

The local counterfactual (HAC-330) and the recorded Google Cloud traversal (HAC-340) are separate runs, and the repository says so. Neither is evidence for the other. This is a bounded experiment, not a safety or production-readiness guarantee.

Problem. Support customers repeat their SLA, setup, open issue and escalation contact every time they come back, because the agent reconstructs context from nothing each session.

System. A support memory agent with explicit working, episodic and semantic memory tiers, a forgetting policy with validity windows and provenance, budgeted recall, and an MCP surface.

The ablation is measured inside the described evaluation setup on synthetic fixtures. It is not a general claim about memory in other products.

Vreko is the developer-intelligence product built at Marcelle Labs. The core application is proprietary. Selected interfaces are public so the integration surface can be inspected and depended on:

• vreko-dev/vreko-cli — @vreko/cli
• vreko-dev/mcp-server — vreko-mcp-server
• vreko-dev/vscode — VS Code extension

Organization: vreko-dev · Documentation: docs.vreko.dev

Qwynn Marcelle separately stewards workspace.json, an Apache-2.0 open standard for committed repository intelligence.

workspace.json is not a Marcelle Labs product. It is an independent standard with its own organization, governance and release authority at workspacejson. Marcelle Labs systems consume it at pinned revisions like any other external dependency — Interlock records that boundary in provenance/manifest.json, and CI enforces it.

Start with a claim, then follow it to the artifact. Every system above links its experiment, its verifier, its deployment record and its stated limits. If a claim here does not resolve to something you can open and check, treat that as a defect and open an issue.