JUDGE TESTING

Verify Titan in under three minutes—or reproduce it locally.

Start with the real browser workflow. The Windows path, MCP smoke, repository gates, and deterministic scale fixture are documented below.

Expected browser test: under 3 minutes

FASTEST PATH

Browser test

The browser demo uses only the bundled Atlas Parcel synthetic fixture and the existing Titan services.

Six checks

  1. Open Judge Tour.
  2. Select Run full demo.
  3. Inspect Problem, Context, and Verify.
  4. Confirm one proposal is approved and one is rejected.
  5. Confirm the export is approved-only.
  6. Reset the demo and confirm the pending baseline returns.
Open Judge Tour

Expected verified evidence

  • Current backend suite: Unavailable/Unavailable passing tests.
  • Public Atlas fixture: Unavailable canonical notes and Unavailable emitted sources.
  • Unavailable-token canonical Atlas benchmark.
  • Unavailable/Unavailable public Atlas tests.
  • Correct implementation returns PASS.
  • Missing tenant test returns WARNING.
  • Legacy fallback restored returns FAIL.
  • One approved and one rejected proposal.
  • Markdown, JSONL, and manifest export.
  • Original Vault unchanged.

LOCAL PATH

Windows 10/11 x64

Titan’s hackathon build is certified only on Windows 10/11 x64. macOS and Linux are not claimed as certified release platforms.

Install, build, and start

Current product: Titan Unavailable · build Unavailable. Runtime: Node.js 20+; verified with v24.16.0.

cd titan-backend
npm ci
npm.cmd run typecheck
npm.cmd run build
npm.cmd start

Open http://127.0.0.1:3000/build-week-demo.

Codex MCP setup

Build Titan, open the repository in Codex, and connect the local Titan MCP server from your Codex configuration. The local STDIO command is:

node titan-backend/dist/mcp/server.js

Confirm the bounded public fixture exposes Unavailable public Atlas tools. This is the canonical public demo catalog, not Titan's global Unavailable-tool workspace catalog.

  • Loading tool catalog…

Smoke test

cd titan-backend
npm.cmd run mcp:smoke

REPOSITORY VERIFICATION

Run every release gate.

These commands cover install integrity, TypeScript, the full backend, build output, tracked-source secrets, Atlas Core, MCP, and Atlas Expanded.

cd titan-backend
npm ci
npm.cmd run typecheck
npm.cmd test
npm.cmd run build
npm.cmd run check:secrets
npm.cmd run mcp:smoke

cd ..\demo\sample-project
npm.cmd test

cd ..\..
node demo\expanded-scale\generate.mjs --verify
node --test demo\expanded-scale\generate.test.mjs
git diff --check

KNOWN LIMITATIONS

A narrow, truthful judge path.

The public experience is deliberately synthetic and restricted. It is not a hosted multi-tenant Titan workspace.

Windows certification only

The submission does not claim a certified macOS or Linux build.

Bundled synthetic data

No arbitrary Vault upload, filesystem path, provider configuration, or command is accepted.

Local Codex required for MCP

The browser demonstrates Titan services; the full MCP loop requires an authenticated Codex session and local STDIO setup.

No physical Vault organization

Titan does not automatically move or rewrite a real Vault in this submission.

No hosted embeddings required

The Build Week path uses local FTS5 plus available graph and metadata signals.

Explicit review remains required

New outcomes are proposals until a person approves or rejects them.

START HERE

Run the real synthetic workflow.

Judge Tour explains the value; Technical Inspector exposes every source, score, rule, and artifact.

Judge TourTechnical InspectorBuild Week evidence