Feature.graph product tour Silent screen recording with on-screen chapter descriptions. Waiting time and navigation pauses are edited out. Real repository mapping uses Feature.graph itself; build, terminal, and code views use an isolated demonstration app. No private source or private GitHub URLs are shown. Setup, design previews, and GitHub publication controls are distinguished from completed actions in the captions. 00:00:03 — Product Home A starting point for capabilities, open decisions, recent work, and project notes. 00:00:11 — Project setup Open a local repository or start from an app idea. Setup options shown here. 00:00:32 — Connected agents and GitHub Use existing local sign-ins for Claude Code, Codex, and GitHub. 00:00:47 — Real repository map Feature.graph mapping itself: 120 features across 187 project files. 00:00:54 — Focused map and feature evidence Narrow the map to one capability and inspect its supporting evidence. 00:01:13 — Repository understanding Explore the product summary, incomplete capabilities, and areas needing review. 00:01:48 — Project settings Keep a project goal attached to the work. Goal changes preserve earlier intent. 00:02:06 — Describe a change Request a Completed filter for a small demonstration app. 00:02:23 — Review the proposal Review the intended outcome, affected areas, preserved behavior, and planned checks. 00:02:33 — Desktop and mobile design previews A generated design concept, shown before implementation. Example data; not a working app. 00:02:45 — Implement with a coding agent Start the real Codex build. Execution choices include local and cloud modes. 00:02:55 — Project files and editor Browse project files beside the workspace. Only demonstration source is shown. 00:03:04 — Review a completed implementation The real build changes three files and passes nine configured checks. 00:03:13 — Try the working app All tasks shows three items; Open only shows two; Completed shows one. Keyboard tested. 00:03:27 — Checks and change evidence Inspect nine passing checks, the checked revision, and the configured command. 00:03:34 — Inspect the changed files Read the saved implementation before deciding whether to keep it. 00:03:50 — Keep the reviewed change Review the diff and manual tryout, then keep the change locally. 00:04:08 — Saved product history The accepted change appears on Product Home. Keeping code does not publish it. 00:04:13 — Feature history and decisions The feature retains its request, plan, design preview, build, and acceptance history. 00:04:30 — Interactive terminal Run npm test in the built-in shell beside the live app. Nine tests pass. 00:04:45 — Preview and app configuration Configure the startup command and local URL, or connect an already running app. 00:05:01 — Ask about the product Ask a question about the code without requesting a file change. 00:05:07 — Project conversation with evidence The saved answer cites project files and distinguishes inspected evidence from uncertainty. 00:05:21 — Map freshness and scan controls Review how source checks are queued, run a check, or pause automatic checks. 00:05:31 — Reconcile the map with new code Source assessments are reviewed separately from code acceptance and runtime verification. 00:05:35 — Suggested next steps Inspect a proposed improvement and its tradeoff. Suggestions remain ideas until built. 00:05:44 — Commands and activity logs Inspect command output and the activity recorded during the build. 00:05:51 — GitHub publishing controls Choose repository name and visibility. No repository is created in this tour. 00:06:01 — A connected product workspace Move between the product map, active changes, and the evidence behind decisions.