Skip to content

Technology Stack

Matthew Feroz edited this page Sep 30, 2026 · 2 revisions

Technology stack

Checked against the public source at 3567263 on September 30, 2026. Package versions describe source requirements, not a fresh verification of a hosted deployment or installed worker.

Technology Source baseline Responsibility
React / TypeScript / Vite Manifest and frozen Bun lockfile Browser UI and production frontend bundle
Bun bun@1.4.0 project package manager Dependency installation, build scripts, unit tests, local tooling
Node.js CLI requires 22+ Installed CLI, daemon, detached supervisor, hosted actions
Heval CLI Source package 0.2.0 Pairing, setup, provider connection, daemon, local result viewing
WorkOS AuthKit React SDK ^0.16.2 Sign-in and identity tokens
Convex SDK ^1.45.0 Backend functions, transactions, subscriptions, durable queue state, reports and permissions
Vercel Managed service Frontend hosting and authenticated export download endpoint
Linux Required for connected runner Operator-controlled execution worker
Python / Harbor Python 3.12+ / Harbor 0.23.0 Portable task, harness, environment, trial, verifier orchestration
Docker Engine / Compose Available to worker account Disposable task environments; record actual image/engine identifiers for reproducibility
Coding harnesses Approved profiles; record actual versions Agents under evaluation, including Codex, Claude Code, Pi, OpenCode, Terminus 2; Oracle checks reference execution
Model providers / Merge Gateway Selected model and serving vendor Remote inference; credentials remain on worker
Vega / Vega-Lite / Vega Embed 6.4.0 / 6.4.3 / 7.1.0 manifest Shared chart recipes and browser/report rendering
Vercel Sandbox / Blob SDK 3.3.0 / 2.8.0 manifest Chromium presentation rendering and private export storage
GitHub Actions / ESLint / Bun tests / Vitest / Playwright Repository workflow and frozen lockfile Automated verification, installed-package checks, browser behavior
Markdown / Mermaid C4 and sequence GitHub-managed renderer Architecture and assignment artifacts

Actual harness installation dependencies, mutable base image tags, and provider model aliases are not automatically frozen by a source dependency pin. Retain task hashes and record actual execution versions for published comparisons. Public synthetic examples are demonstrations, not measured results.

There is no separately operated Postgres, Redis, Kubernetes cluster, automatic cloud evaluation provisioning, or central raw-artifact archive in the implemented primary path. The older Bun HTTP/WebSocket workbench and direct Harbor workflows remain separate supporting paths.

Application manifest, Bun lockfile, CLI manifest, Harbor pin, worker requirements, and deployment setup.

Clone this wiki locally