repo map
Use this map when you already understand the product and now need to know where each lane actually lives.
This page answers one practical question: where does everything live in this repo? It is a routing page, not a second homepage. In other words, open this after the front door has already done its job.
use this page for
- Question
- Which file or lane should I open next?
- Best moment
- after you already understand the product sentence and first success path
- Not for
- first-time product orientation
front door hierarchy
The map only works if the order stays honest.
Primary front door
GitHub repo + CLI quickstart
This is still the first path for a new visitor.
First visible proof
Archive shell proof page
This explains what the repo can already prove without turning proof into hosted-product theatre.
Secondary surfaces
Reports, integration, governance
These lanes are real and useful, but they still should not own the first screen.
choose by intent
Open the lane that matches the question you actually have.
front door
How do I get one successful result?
Open the GitHub front door because the flagship packet still lives there.
visual companion
Can I get the shortest visual walkthrough first?
Open the promo reel when a short motion pass will orient you faster than more prose.
sharing lane
What should I share once the product story is already clear?
Open the launch kit for second-ring distribution-prep assets and copy.
proof
What does the first proof actually prove?
Open archive shell proof when the proof boundary itself is the question.
renderers
Where are transcripts, reports, and evidence rendered?
src/output/ is the visible shell layer.
connectors
Where are connector boundaries defined?
src/connectors/ is the source adapter layer.
contracts
Where does archive and governance logic live?
src/core/ is the contract and decision layer.
integration lane
Where is the repo-owned integration lane?
docs/integrations/ is the integration pack surface.
reference shelf
Where are the truth boundaries and upstream reading lists?
docs/reference/ is the constraint shelf.
repository layout
Think in lanes, not just folders.
Entry
src/cli.rs
The CLI entrypoint and command routing. This is still the operational front door.
Local execution UI
src/ui/
The local Export Cockpit WebUI. It auto-discovers workspace-relevant Codex threads and workspace-local Claude sessions, runs the matching export path, then opens the archive shell.
Source adapters
src/connectors/
Codex and Claude Code source boundaries. This is where transcript intake rules live.
Contracts
src/core/
Archive, search, evidence, workbench case stitching, official-answer lifecycle, and host-safety rules. This is the product logic shelf.
Readable surfaces
src/output/
Archive shell, family case views, official-answer workflow cards, search report, and integration evidence rendering. This is the visible workbench layer.
Public docs
docs/
The companion public docs surface. It explains, routes, and proves, but does not replace the CLI front door.
Promo lane
docs/promo-reel.md
The compact visual companion for first-time reviewers who want the shortest proof-aligned walkthrough.
Launch lane
docs/launch-kit.md
The second-ring distribution-prep shelf for channel-ready copy, asset routing, and packet-safe sharing.
Design law
design-system/
The repo-owned visual and IA doctrine for front door and workbench shells.
Integration lane
docs/integrations/
Repo-owned integration pack guidance for Codex, Claude Code, and related side lanes.
Reference shelf
docs/reference/
Upstream contracts, reading lists, and host-safety boundaries. Use this when you need truth-source detail.
Governance artifacts
policies/
Integration evidence policy packs and governance baselines. This is the local rulebook shelf.
public truth boundary
What this map should help you avoid misunderstanding.
- Pages is a public companion surface, not a hosted runtime
- archive shell proof is a tracked explanation page, not a live app
- integration pack and governance MCP bridge remain secondary surfaces
what to do next
Leave the map as soon as it has done its job.
- go back to the GitHub front door for first success
- open archive shell proof for proof interpretation
- open promo reel for the shortest visual walkthrough
- open launch kit for second-ring sharing and distribution-prep
- open distribution packet ledger only when lane truth matters