Legacy Codex
Legacy Codex is the canonical human-facing product for preserving context, clarifying what matters, choosing the next meaningful action, and resuming without rebuilding the whole situation.
The one answer
- Canonical repository:
edwardemoryphotography/legacy-codex
- Canonical production URL:
https://legacy-codex.vercel.app
- Primary loop:
Capture -> Clarify -> Constrain -> Choose -> Act -> Resume
Foundry is the builder and operations environment behind Legacy Codex. Routing, evidence, events, and control-plane infrastructure are internal capabilities, not separate products the owner must coordinate during normal use.
Start here
AGENTS.md — repository instructions and verification gates.docs/architecture/legacy-codex-product-definition.md — canonical product boundary.docs/architecture/canonical-source-graph.md — where each kind of truth lives and what is historical.docs/architecture/data-ownership.md — canonical tables and transitional stores.PROJECT_STATUS.md — dated implementation and deployment state.
The cross-system cognitive doctrine remains the Goose Cookbook in edwardemoryphotography/codex-system-architecture/notion-wiki/docs/GOOSE-COOKBOOK.md.
Its North Star is preserving human intent so another intelligence can reconstruct, execute, verify, and continue it. The reviewed runtime projection is src/lib/cognitiveDoctrine.ts, consumed by the analysis, operation and project-review model routes. In the app, open Codex → Root → North Star — Goose Cookbook, or search Goose, to read the origin lesson, MasterChef method, primary source, and current capability limits.
On Mission, Review project reconstructs the saved outcome using real account-scoped sources, reads supporting records from selected related projects, and critiques its own proposal once. Why this → Lessons carried forward lets the owner edit and confirm a proposed lesson, state when it applies, and choose project-only or account-wide scope. Later relevant reviews read active confirmed lessons; Stop using this lesson retires a rule while retaining its history. Reviews are proposals, lessons are human-confirmed operating rules, and neither is verified evidence. Project-review provider calls require an explicit review; reload only restores current cached project reasoning. The existing owner access gate still applies, so sharing the URL does not grant model access.
Local development
npm ci
npm test
npm run lint
npx tsc --noEmit
npm run build
npm run dev
The application requires a Next.js-aware deployment because /api/analyze is a server route. Never infer production behavior from a successful local build or merged pull request.
Release naming
The product name is Legacy Codex. Historical labels such as v24, v27, v35.3, and v38 are provenance, not the current product identity. Future public versions are ordinary software release tags created only when an actual release policy needs them.
