LIVE MCP EVIDENCECodex connected through Unavailable public Atlas tools
Bounded, reproducible, and safe for public evaluation.
OPENAI BUILD WEEK 2026
Titan
Give Codex the right project memory before it changes your code.
Titan separates current decisions from legacy guidance, verifies the implementation, and returns approved knowledge to Obsidian.
Verifiable project memory for Codex
Atlas Parcel Demo · Safe synthetic fixture
Local-onlyMCP-readyNo separate API keyUses your Codex session
REPRODUCIBLE SCALE FIXTUREUnavailable deterministic notes
Unavailable source notes + Unavailable distractors + Unavailable late signal
node demo/expanded-scale/generate.mjs --verifyCould not load the Atlas Parcel demo.
Technical details
Request failed.ONE-CLICK REAL WORKFLOW
See Titan close the memory loop
Preview, compile, verify, review, and export the fixed Atlas Parcel fixture through existing Titan services.
Ready · 7 deterministic actions
- VaultPending
- CompilePending
- VerifyPending
- RecordPending
- ReviewPending
- ExportPending
JUDGE TOUR
Five steps from noisy memory to verified context
Each view below is backed by the same real Atlas Parcel workflow shown in the Technical Inspector.
STEP 01 / PROBLEM
Project memory changes. Old guidance does not disappear.
Without state-aware context, a coding agent can receive both the obsolete fallback and the current ownership rule.
Restore the fallback
LegacyTrackingAdapterSuperseded ownership from an earlier architecture.
Mixed contextWrong file · wrong rule · avoidable risk
Use the tenant-scoped repository
PackageRepositoryThe committed source of truth for tracking lookup.
Titan separates current guidance from legacy and proposed memory before Codex acts on it.
Loading the real Atlas Parcel Vault preview…
STEP 02 / CONTEXT
Less context. Better separated.
Titan compiles a bounded brief from traceable local sources before Codex starts work.
26Candidates
13Emitted sources
Duplicated and misclassified legacy context.
13Candidates
12Emitted sources
Canonical Atlas benchmark. Current, superseded, and proposed guidance separated.
The canonical Atlas fixture produced a 39% smaller context after duplicate and state-aware filtering. This is fixture-specific.
CODEX BRIEF
The implementation contract Codex receives
The Vault preview is loading. Compile becomes available when it succeeds.
STEP 03 / VERIFY
Deterministic outcomes, justified by the pack.
Select any committed scenario. Titan evaluates real changed-file, test, and constraint evidence—without a model call.
Compile context, then select a scenario to see its rule and cited source.
STEP 04 / REVIEW
Codex proposes. A person decides.
Titan never turns a model transcript into durable project memory. Atomic outcomes remain proposed until explicit review.
No automatic memory writes
Approve useful guidance and reject redundant or unsafe proposals before export.
Run verification and record the outcome to create real reviewable proposals.
STEP 05 / EXPORT
Approved memory stays portable—and the Vault stays untouched.
Titan exports only explicitly approved items in open formats with stable provenance.
Awaiting explicit proposal review
Approve at least one proposal to enable the real approved-only export.
OBSIDIAN-COMPATIBLE PREVIEW
Approved memory, visibly structured
The approved note preview appears after export. Runtime IDs are never hardcoded.
Open, reviewable, local-first
Markdown remains readable in Obsidian; JSONL and the manifest preserve machine-readable memory.
TECHNICAL INSPECTOR
Inspect every source, score, rule, and review
Local-first project memory, compiled into a bounded and reviewable Codex context pack.
Titan exposes the full global workspace toolset locally. The public Atlas demo intentionally uses a bounded canonical catalog.
Loading the fixed Atlas Parcel Vault…
Before hardening
26 to 13candidates to emitted sources3,447 estimated tokens · duplicated and misclassified legacy context
Canonical Atlas benchmark
13 to 12candidates to emitted sources2,091 estimated tokens · 1 grouped duplicate · current, superseded, and proposed guidance separated
39% less context in the canonical Atlas benchmark, with current, historical, and proposed guidance separated.Codex-ready context
Bounded implementation brief
After compilation, current decisions stay active while superseded legacy context is visibly separated.
Completion verification
Deterministic evidence check
Compile a context pack to run deterministic evidence scenarios.
Memory proposals
Atomic outcomes only
Run verification, then record the structured demo outcome to create reviewable proposals.
Approved export
Open, portable formats
Only explicitly approved proposals can be exported. The original vault remains read-only.