Skip to content
View qmarcelle's full-sized avatar
🧠
Building AI Behavioral Intelligence @ Vreko
🧠
Building AI Behavioral Intelligence @ Vreko

Block or report qmarcelle

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
qmarcelle/README.md

Qwynn Marcelle

I build repository intelligence for coding agents.

I’m the founder of Marcelle Labs and the creator of Vreko. Vreko turns repository structure, history, and constraints into durable, machine-readable evidence that helps agents make better engineering decisions.

The open substrate beneath that work is workspace.json—a portable specification for describing what agents need to understand about a codebase without repeatedly rediscovering it.

What I’m building

  • Vreko CLI
    Local-first repository intelligence and agent-facing development workflows.

  • agents-audit
    The reference producer, validator, and CLI for workspace.json.

  • Codex MCP
    Deterministic repository evidence and change-scope safeguards for Codex.

  • SOPR MCP
    Research and tooling for reducing agent tool-selection overhead through structured routing.

Current focus

  • Machine-readable repository context
  • MCP servers and agent interoperability
  • Evidence-driven change safeguards
  • Repository history and co-change intelligence
  • Agent memory, routing, and context efficiency
  • TypeScript, Node.js, Next.js, VS Code, and GitHub Actions

Open-source approach

I favor small, compatibility-first contributions that solve a maintainer’s existing problem before proposing a broader integration.

A recent example: my additive workspace.json compatibility change for Buildomator shipped in v3.4.6 with the original authorship and regression coverage preserved.

I’m currently exploring reporter and adapter boundaries where established analysis tools can produce portable repository evidence without taking a dependency on the full workspace.json ecosystem.

Working thesis

Agents should not have to rediscover the same repository facts every session—and safety-critical decisions should be grounded in inspectable evidence, not prompt folklore.

Connect

Pinned Loading

  1. vreko-dev/vreko-cli vreko-dev/vreko-cli Public

    The Vreko CLI — local behavioral intelligence for AI-assisted development.

    1

  2. vreko-dev/sopr-mcp vreko-dev/sopr-mcp Public

    SOPR-MCP: Token-efficient protocol routing for AI tool systems

    TypeScript 1

  3. workspace-json/codex-mcp workspace-json/codex-mcp Public

    Portable repository history that changes Codex's plan before an evidenced risky edit lands.

    TypeScript 1

  4. workspace-json/agents-audit workspace-json/agents-audit Public

    Canonical monorepo for agents-audit, @workspacejson/spec, and @workspacejson/rules

    TypeScript