Before Build Week
- TypeScript/Fastify application shell
- Local SQLite memory foundation
- Obsidian Vault indexing
- Basic retrieval and graph view
- Optional BYOK chat providers
OPENAI BUILD WEEK 2026
This page separates Titan’s pre-existing local memory foundation from the Build Week extension using a baseline tag, branch, commit history, architecture evidence, and reproducible test gates.
BEFORE / AFTER BOUNDARY
The baseline tag preserves the source state before the submission period. Build Week commits implement the context, protocol, verification, review, export, and judge paths.
CODEX COLLABORATION
GPT-5.6 supplied the coding capability. Titan supplied the bounded project memory, strict rules, methodology, provenance, and verification loop.
TitanCodexTitanHuman
Titan
Titan compiled the current project memory.
Titan
Visual, CSS, and Mobile methodology was selected.
Codex
GPT-5.6 and Codex executed the code changes.
Titan
Titan checked changed files, tests, constraints, and evidence.
Titan
Durable outcomes were created as reviewable proposals.
Human
Nothing was approved or exported automatically.
Honest checkpoint: verifier WARNING · proposals remained proposed until review · human approval required · no automatic approval. Private session content and personal filesystem paths stay excluded.
ARCHITECTURE CHANGES
The Build Week extension stays local-first and reuses Titan Core services rather than duplicating retrieval or persistence in the demo.
Obsidian Markdown
| preview + local index
SQLite FTS5 -> explainable ranking -> Context Compiler
|
Codex session <- Unavailable public Atlas tools over local STDIO
| changed files + structured test evidence
Deterministic verification -> atomic proposals
| explicit human approval
Obsidian Markdown + JSONL + manifest
CURRENT PRODUCT / PUBLIC DEMO / HISTORICAL
Current product status, the bounded public Atlas fixture, and frozen benchmark evidence remain explicitly separated.
Current deterministic backend test gate.
Canonical Atlas Parcel verification suite.
Distinct global workspace and bounded demo surfaces.
Frozen benchmark context pack.
Historical documented comparison.
Reproducible Atlas Expanded scale.
PASS · WARNING · FAIL
The public workflow writes only generated demo state.
CHRONOLOGICAL COMMITS
The list is chronological and intentionally excludes private thread content. Hashes identify the implementation boundary in the Build Week branch.
loadingLoading commit evidence…KNOWN LIMITATIONS
Scope is part of credibility. The public path demonstrates the complete loop without presenting a synthetic fixture as customer scale or a Windows build as cross-platform certification.
Only Windows 10/11 x64 is claimed for the tested local build.
Atlas Core and Atlas Expanded are fictional, reproducible judge fixtures.
The full Codex integration requires a local authenticated Codex session and STDIO process.
The original Vault remains read-only; physical reorganization is outside this submission.
Verification is deterministic and bounded to persisted context, files, constraints, and supplied tests.
This build exposes the verified product, demo, testing, and Build Week routes without claiming external release destinations.
INSPECT IT
Start with the Judge Tour, inspect every source in the Technical Inspector, or reproduce the workflow locally.