{
  "schema_version": 2,
  "meta": {
    "build_id": "CODEX-YAHOO-FINANCE-COLLECTOR",
    "slug": "yahoo-finance-collector",
    "title": "Yahoo Finance Data Collector",
    "subtitle": "Separate price provenance, validation and repeatable storage.",
    "description": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "one_sentence_description": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "target_user": "A motivated beginner with permission to work in a private practice folder.",
    "skill_level": "beginner",
    "estimated_time": "100–150 minutes",
    "category": "Guided Build",
    "tags": [
      "yahoo-finance-collector",
      "verified practice",
      "chatgpt_codex"
    ],
    "prerequisites": [
      "Permission to use a dedicated workspace",
      "A browser and terminal",
      "Read each platform-specific prerequisite before installation"
    ],
    "required_accounts": [],
    "required_software": [
      "Modern browser",
      "Python 3.10+ for downloadable drills"
    ],
    "required_hardware": [
      "A computer with space for the practice files",
      "Second drive for the disaster-recovery checkpoint"
    ],
    "expected_cost": "Free practice; existing tool accounts may have plan limits.",
    "final_outcome": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "platforms": [
      "windows",
      "macos",
      "linux"
    ],
    "version": "2.0",
    "author": "chatgpt_codex",
    "source_checked": "2026-10-05",
    "verification_status": "Created; automated browser and project checks recorded separately. Live account/OS verification is never inferred from browser completion."
  },
  "user_outcome": {
    "before": "The learner has no reproducible, checked workflow for yahoo finance data collector.",
    "after": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "finished_product": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics."
  },
  "learning_objectives": [
    "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
    "Two synthetic daily bars satisfy the OHLC/volume/date contract.",
    "The second run still reports total=2.",
    "The isolated environment imports yfinance and its installed version is recorded.",
    "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
    "The invalid OHLC range produces an error and no successful FINANCE PASS receipt."
  ],
  "lessons": [
    {
      "lesson_id": "L01",
      "title": "Define the data contract",
      "purpose": "A stock split changes raw prices. Silently mixing adjusted/unadjusted data can create false returns; this course teaches collection, not investment decisions.",
      "estimated_time": "6 min",
      "learning_objective": "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
      "lessons_before_this": [],
      "lessons_after_this": [
        "L02"
      ]
    },
    {
      "lesson_id": "L02",
      "title": "Prepare and inspect fixtures",
      "purpose": "A dedicated folder makes mistakes easy to diagnose and keeps real project files separate.",
      "estimated_time": "12 min",
      "learning_objective": "Two synthetic daily bars satisfy the OHLC/volume/date contract.",
      "lessons_before_this": [
        "L01"
      ],
      "lessons_after_this": [
        "L03"
      ]
    },
    {
      "lesson_id": "L03",
      "title": "Create the local archive",
      "purpose": "FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
      "estimated_time": "12 min",
      "learning_objective": "The second run still reports total=2.",
      "lessons_before_this": [
        "L02"
      ],
      "lessons_after_this": [
        "L04"
      ]
    },
    {
      "lesson_id": "L04",
      "title": "Add the optional live dependency",
      "purpose": "yfinance is an independent open-source project, not an official Yahoo service with guaranteed availability. Do not change global Python dependencies.",
      "estimated_time": "6 min",
      "learning_objective": "The isolated environment imports yfinance and its installed version is recorded.",
      "lessons_before_this": [
        "L03"
      ],
      "lessons_after_this": [
        "L05"
      ]
    },
    {
      "lesson_id": "L05",
      "title": "Fetch a bounded live sample",
      "purpose": "The exchange session date and UTC retrieval timestamp mean different things. Prices may be delayed, corrected or incomplete.",
      "estimated_time": "6 min",
      "learning_objective": "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
      "lessons_before_this": [
        "L04"
      ],
      "lessons_after_this": [
        "L06"
      ]
    },
    {
      "lesson_id": "L06",
      "title": "Diagnose missing and invalid prices",
      "purpose": "Empty live data is a failure to investigate, not proof the symbol has no history.",
      "estimated_time": "6 min",
      "learning_objective": "The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
      "lessons_before_this": [
        "L05"
      ],
      "lessons_after_this": [
        "L07"
      ]
    },
    {
      "lesson_id": "L07",
      "title": "Deliver the collector with limits",
      "purpose": "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
      "estimated_time": "6 min",
      "learning_objective": "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
      "lessons_before_this": [
        "L06"
      ],
      "lessons_after_this": [
        "L08"
      ]
    },
    {
      "lesson_id": "L08",
      "title": "Build Bot Better — protect and recover",
      "purpose": "The September 23 BuildBotsBetter profile wipe removed Desktop, Documents and hidden agent memory together. Repeatable onboarding protects the knowledge needed to recover.",
      "estimated_time": "30 min",
      "learning_objective": "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
      "lessons_before_this": [
        "L07"
      ],
      "lessons_after_this": []
    }
  ],
  "steps": [
    {
      "title": "Choose symbols, dates and adjustment policy",
      "purpose": "A stock split changes raw prices. Silently mixing adjusted/unadjusted data can create false returns; this course teaches collection, not investment decisions.",
      "user_action": "Open data-dictionary.md. Record the intended symbols, exchange/session dates, daily interval and whether you need unadjusted or adjusted prices. This starter stores unadjusted OHLCV; use the synthetic DEMO series first.",
      "explanation": "A stock split changes raw prices. Silently mixing adjusted/unadjusted data can create false returns; this course teaches collection, not investment decisions.",
      "estimated_time": "6 min",
      "action_type": "inspect",
      "commands": {
        "all": ""
      },
      "command_type": "shell",
      "required_inputs": [
        "data-dictionary.md"
      ],
      "expected_result": "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
      "resources": [
        "data-dictionary.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Choose symbols, dates and adjustment policy",
        "success_condition": "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
        "how_to_verify": "Record the contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify choose symbols, dates and adjustment policy?",
          "answer": "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use data-dictionary.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to choose symbols, dates and adjustment policy. The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
        "demo": "Open data-dictionary.md. Record the intended symbols, exchange/session dates, daily interval and whether you need unadjusted or adjusted prices. This starter stores unadjusted OHLCV; use the synthetic DEMO series first.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate choose symbols, dates and adjustment policy",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Open data-dictionary.md. Record the intended symbols, exchange/session dates, daily interval and whether you need unadjusted or adjusted prices. This starter stores unadjusted OHLCV; use the synthetic DEMO series first. The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
        "on_screen_text": [
          "Choose symbols, dates and adjustment policy",
          "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC."
        ],
        "screen_recording_instructions": [
          "Open data-dictionary.md. Record the intended symbols, exchange/session dates, daily interval and whether you need unadjusted or adjusted prices. This starter stores unadjusted OHLCV; use the synthetic DEMO series first.",
          "Inspect the result: The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Open data-dictionary.md. Record the intended symbols, exchange/session dates, daily interval and whether you need unadjusted or adjusted prices. This starter stores unadjusted OHLCV; use the synthetic DEMO series first.",
          "The contract identifies daily session dates, unadjusted prices, volume, source and retrieval UTC."
        ]
      },
      "step_id": "L01-S01",
      "lesson_id": "L01"
    },
    {
      "title": "Set up the practice folder",
      "purpose": "A dedicated folder makes mistakes easy to diagnose and keeps real project files separate.",
      "user_action": "Download the resource ZIP at the top of this Build. Extract it into a new folder you own (for example C:\\BBBPractice on Windows, or ~/bbb-practice on macOS/Linux). Open a terminal in the extracted folder. Run the version command for your platform. All subsequent commands assume this folder.",
      "explanation": "A dedicated folder makes mistakes easy to diagnose and keeps real project files separate.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python --version\nGet-Location\nGet-ChildItem",
        "macos": "python3 --version\npwd\nls",
        "linux": "python3 --version\npwd\nls"
      },
      "command_type": "shell",
      "required_inputs": [],
      "expected_result": "Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
      "resources": [],
      "checkpoint": {
        "what_is_being_checked": "Set up the practice folder",
        "success_condition": "Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
        "how_to_verify": "Record python reports version 3.10 or newer and the terminal is in the extracted resource folder. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "Python is 3.10 or newer.",
          "The listed files match the downloaded resources."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "Python or a file is not found",
          "likely_cause": "The terminal may be outside the extracted ZIP or Python may not be on PATH.",
          "diagnostic_question": "Does the file list include the resource named by the next step?",
          "fix": "Install Python from python.org with the PATH option; reopen the terminal and change into the extracted folder.",
          "alternative_fix": "Use py -3 on Windows if the Python launcher is installed. macOS/Linux commands use python3.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Install Python from python.org with the PATH option; reopen the terminal and change into the extracted folder."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify set up the practice folder?",
          "answer": "Python reports version 3.10 or newer and the terminal is in the extracted resource folder. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use your saved work from the previous step. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to set up the practice folder. Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
        "demo": "Download the resource ZIP at the top of this Build. Extract it into a new folder you own (for example C:\\BBBPractice on Windows, or ~/bbb-practice on macOS/Linux). Open a terminal in the extracted folder. Run the version command for your platform. All subsequent commands assume this folder.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Install Python from python.org with the PATH option; reopen the terminal and change into the extracted folder.",
        "help": "Does the file list include the resource named by the next step?"
      },
      "video": {
        "purpose": "Demonstrate set up the practice folder",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Download the resource ZIP at the top of this Build. Extract it into a new folder you own (for example C:\\BBBPractice on Windows, or ~/bbb-practice on macOS/Linux). Open a terminal in the extracted folder. Run the version command for your platform. All subsequent commands assume this folder. Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
        "on_screen_text": [
          "Set up the practice folder",
          "Python reports version 3.10 or newer and the terminal is in the extracted resource folder."
        ],
        "screen_recording_instructions": [
          "Download the resource ZIP at the top of this Build. Extract it into a new folder you own (for example C:\\BBBPractice on Windows, or ~/bbb-practice on macOS/Linux). Open a terminal in the extracted folder. Run the version command for your platform. All subsequent commands assume this folder.",
          "Inspect the result: Python reports version 3.10 or newer and the terminal is in the extracted resource folder.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "Python reports version 3.10 or newer and the terminal is in the extracted resource folder."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Download the resource ZIP at the top of this Build. Extract it into a new folder you own (for example C:\\BBBPractice on Windows, or ~/bbb-practice on macOS/Linux). Open a terminal in the extracted folder. Run the version command for your platform. All subsequent commands assume this folder.",
          "Python reports version 3.10 or newer and the terminal is in the extracted resource folder."
        ]
      },
      "step_id": "L02-S01",
      "lesson_id": "L02"
    },
    {
      "title": "Validate the sample bars",
      "purpose": "A parser should reject broken ranges or NaN rather than store a plausible-looking number.",
      "user_action": "Open prices.json. Check low <= open/close <= high, positive finite prices, nonnegative volume and unique symbol/date pairs. These DEMO records are not market quotes.",
      "explanation": "A parser should reject broken ranges or NaN rather than store a plausible-looking number.",
      "estimated_time": "6 min",
      "action_type": "inspect",
      "commands": {
        "all": ""
      },
      "command_type": "shell",
      "required_inputs": [
        "prices.json",
        "data-dictionary.md"
      ],
      "expected_result": "Two synthetic daily bars satisfy the OHLC/volume/date contract.",
      "resources": [
        "prices.json",
        "data-dictionary.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Validate the sample bars",
        "success_condition": "Two synthetic daily bars satisfy the OHLC/volume/date contract.",
        "how_to_verify": "Record two synthetic daily bars satisfy the OHLC/volume/date contract. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "Two synthetic daily bars satisfy the OHLC/volume/date contract.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. Two synthetic daily bars satisfy the OHLC/volume/date contract.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify validate the sample bars?",
          "answer": "Two synthetic daily bars satisfy the OHLC/volume/date contract. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use prices.json, data-dictionary.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to validate the sample bars. Two synthetic daily bars satisfy the OHLC/volume/date contract.",
        "demo": "Open prices.json. Check low <= open/close <= high, positive finite prices, nonnegative volume and unique symbol/date pairs. These DEMO records are not market quotes.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate validate the sample bars",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Open prices.json. Check low <= open/close <= high, positive finite prices, nonnegative volume and unique symbol/date pairs. These DEMO records are not market quotes. Two synthetic daily bars satisfy the OHLC/volume/date contract.",
        "on_screen_text": [
          "Validate the sample bars",
          "Two synthetic daily bars satisfy the OHLC/volume/date contract."
        ],
        "screen_recording_instructions": [
          "Open prices.json. Check low <= open/close <= high, positive finite prices, nonnegative volume and unique symbol/date pairs. These DEMO records are not market quotes.",
          "Inspect the result: Two synthetic daily bars satisfy the OHLC/volume/date contract.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "Two synthetic daily bars satisfy the OHLC/volume/date contract."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Open prices.json. Check low <= open/close <= high, positive finite prices, nonnegative volume and unique symbol/date pairs. These DEMO records are not market quotes.",
          "Two synthetic daily bars satisfy the OHLC/volume/date contract."
        ]
      },
      "step_id": "L02-S02",
      "lesson_id": "L02"
    },
    {
      "title": "Store the fixture",
      "purpose": "FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
      "user_action": "Run finance_collector.py with --fixture prices.json. Inspect prices.sqlite and retain the printed source label.",
      "explanation": "Keep the input and the observed result together so you can reproduce this action later.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python finance_collector.py --fixture prices.json",
        "macos": "python3 finance_collector.py --fixture prices.json",
        "linux": "python3 finance_collector.py --fixture prices.json"
      },
      "command_type": "shell",
      "required_inputs": [
        "finance_collector.py",
        "prices.json"
      ],
      "expected_result": "FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
      "resources": [
        "finance_collector.py",
        "prices.json"
      ],
      "checkpoint": {
        "what_is_being_checked": "Store the fixture",
        "success_condition": "FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
        "how_to_verify": "Record fINANCE PASS reports written=2 total=2 source=synthetic-fixture. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [
          "FINANCE PASS",
          "total=2",
          "synthetic-fixture"
        ],
        "user_visible_success_message": "Evidence saved. FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify store the fixture?",
          "answer": "FINANCE PASS reports written=2 total=2 source=synthetic-fixture. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use finance_collector.py, prices.json. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to store the fixture. FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
        "demo": "Run finance_collector.py with --fixture prices.json. Inspect prices.sqlite and retain the printed source label.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate store the fixture",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Run finance_collector.py with --fixture prices.json. Inspect prices.sqlite and retain the printed source label. FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
        "on_screen_text": [
          "Store the fixture",
          "FINANCE PASS reports written=2 total=2 source=synthetic-fixture."
        ],
        "screen_recording_instructions": [
          "Run finance_collector.py with --fixture prices.json. Inspect prices.sqlite and retain the printed source label.",
          "Inspect the result: FINANCE PASS reports written=2 total=2 source=synthetic-fixture.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "FINANCE PASS reports written=2 total=2 source=synthetic-fixture."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Run finance_collector.py with --fixture prices.json. Inspect prices.sqlite and retain the printed source label.",
          "FINANCE PASS reports written=2 total=2 source=synthetic-fixture."
        ]
      },
      "step_id": "L03-S01",
      "lesson_id": "L03"
    },
    {
      "title": "Prove retries are idempotent",
      "purpose": "Provider corrections can replace a daily bar. A production archive may additionally retain historical revisions.",
      "user_action": "Run the same fixture again. Confirm total remains 2. The upsert replaces the same source/symbol/date values and refreshes retrieved_utc; it does not append duplicates.",
      "explanation": "Provider corrections can replace a daily bar. A production archive may additionally retain historical revisions.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python finance_collector.py --fixture prices.json",
        "macos": "python3 finance_collector.py --fixture prices.json",
        "linux": "python3 finance_collector.py --fixture prices.json"
      },
      "command_type": "shell",
      "required_inputs": [
        "finance_collector.py"
      ],
      "expected_result": "The second run still reports total=2.",
      "resources": [
        "finance_collector.py"
      ],
      "checkpoint": {
        "what_is_being_checked": "Prove retries are idempotent",
        "success_condition": "The second run still reports total=2.",
        "how_to_verify": "Record the second run still reports total=2. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The second run still reports total=2.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [
          "total=2"
        ],
        "user_visible_success_message": "Evidence saved. The second run still reports total=2.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify prove retries are idempotent?",
          "answer": "The second run still reports total=2. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use finance_collector.py. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to prove retries are idempotent. The second run still reports total=2.",
        "demo": "Run the same fixture again. Confirm total remains 2. The upsert replaces the same source/symbol/date values and refreshes retrieved_utc; it does not append duplicates.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate prove retries are idempotent",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Run the same fixture again. Confirm total remains 2. The upsert replaces the same source/symbol/date values and refreshes retrieved_utc; it does not append duplicates. The second run still reports total=2.",
        "on_screen_text": [
          "Prove retries are idempotent",
          "The second run still reports total=2."
        ],
        "screen_recording_instructions": [
          "Run the same fixture again. Confirm total remains 2. The upsert replaces the same source/symbol/date values and refreshes retrieved_utc; it does not append duplicates.",
          "Inspect the result: The second run still reports total=2.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The second run still reports total=2."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Run the same fixture again. Confirm total remains 2. The upsert replaces the same source/symbol/date values and refreshes retrieved_utc; it does not append duplicates.",
          "The second run still reports total=2."
        ]
      },
      "step_id": "L03-S02",
      "lesson_id": "L03"
    },
    {
      "title": "Create an isolated environment",
      "purpose": "yfinance is an independent open-source project, not an official Yahoo service with guaranteed availability. Do not change global Python dependencies.",
      "user_action": "For live retrieval only, create a virtual environment and install requirements-live.txt. Check the yfinance project documentation and Yahoo data terms for your permitted use. Record the installed dependency versions; fixtures do not need this package.",
      "explanation": "yfinance is an independent open-source project, not an official Yahoo service with guaranteed availability. Do not change global Python dependencies.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python -m venv .venv\n.\\.venv\\Scripts\\python.exe -m pip install -r requirements-live.txt\n.\\.venv\\Scripts\\python.exe -m pip freeze",
        "macos": "python3 -m venv .venv\n.venv/bin/python -m pip install -r requirements-live.txt\n.venv/bin/python -m pip freeze",
        "linux": "python3 -m venv .venv\n.venv/bin/python -m pip install -r requirements-live.txt\n.venv/bin/python -m pip freeze"
      },
      "command_type": "shell",
      "required_inputs": [
        "requirements-live.txt"
      ],
      "expected_result": "The isolated environment imports yfinance and its installed version is recorded.",
      "resources": [
        "requirements-live.txt"
      ],
      "checkpoint": {
        "what_is_being_checked": "Create an isolated environment",
        "success_condition": "The isolated environment imports yfinance and its installed version is recorded.",
        "how_to_verify": "Record the isolated environment imports yfinance and its installed version is recorded. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The isolated environment imports yfinance and its installed version is recorded.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. The isolated environment imports yfinance and its installed version is recorded.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify create an isolated environment?",
          "answer": "The isolated environment imports yfinance and its installed version is recorded. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use requirements-live.txt. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to create an isolated environment. The isolated environment imports yfinance and its installed version is recorded.",
        "demo": "For live retrieval only, create a virtual environment and install requirements-live.txt. Check the yfinance project documentation and Yahoo data terms for your permitted use. Record the installed dependency versions; fixtures do not need this package.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate create an isolated environment",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "For live retrieval only, create a virtual environment and install requirements-live.txt. Check the yfinance project documentation and Yahoo data terms for your permitted use. Record the installed dependency versions; fixtures do not need this package. The isolated environment imports yfinance and its installed version is recorded.",
        "on_screen_text": [
          "Create an isolated environment",
          "The isolated environment imports yfinance and its installed version is recorded."
        ],
        "screen_recording_instructions": [
          "For live retrieval only, create a virtual environment and install requirements-live.txt. Check the yfinance project documentation and Yahoo data terms for your permitted use. Record the installed dependency versions; fixtures do not need this package.",
          "Inspect the result: The isolated environment imports yfinance and its installed version is recorded.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The isolated environment imports yfinance and its installed version is recorded."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "For live retrieval only, create a virtual environment and install requirements-live.txt. Check the yfinance project documentation and Yahoo data terms for your permitted use. Record the installed dependency versions; fixtures do not need this package.",
          "The isolated environment imports yfinance and its installed version is recorded."
        ]
      },
      "step_id": "L04-S01",
      "lesson_id": "L04"
    },
    {
      "title": "Request one symbol and inspect provenance",
      "purpose": "The exchange session date and UTC retrieval timestamp mean different things. Prices may be delayed, corrected or incomplete.",
      "user_action": "If your use is permitted, run the live command for one symbol. Inspect the last five available session bars. Capture retrieval time, source and actual date range. A closed market or holiday can reduce rows; do not invent current quotes.",
      "explanation": "The exchange session date and UTC retrieval timestamp mean different things. Prices may be delayed, corrected or incomplete.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": ".\\.venv\\Scripts\\python.exe finance_collector.py --live MSFT --db live-prices.sqlite",
        "macos": ".venv/bin/python finance_collector.py --live MSFT --db live-prices.sqlite",
        "linux": ".venv/bin/python finance_collector.py --live MSFT --db live-prices.sqlite"
      },
      "command_type": "shell",
      "required_inputs": [
        "finance_collector.py",
        "data-dictionary.md"
      ],
      "expected_result": "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
      "resources": [
        "finance_collector.py",
        "data-dictionary.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Request one symbol and inspect provenance",
        "success_condition": "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
        "how_to_verify": "Record a nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify request one symbol and inspect provenance?",
          "answer": "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use finance_collector.py, data-dictionary.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to request one symbol and inspect provenance. A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
        "demo": "If your use is permitted, run the live command for one symbol. Inspect the last five available session bars. Capture retrieval time, source and actual date range. A closed market or holiday can reduce rows; do not invent current quotes.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate request one symbol and inspect provenance",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "If your use is permitted, run the live command for one symbol. Inspect the last five available session bars. Capture retrieval time, source and actual date range. A closed market or holiday can reduce rows; do not invent current quotes. A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
        "on_screen_text": [
          "Request one symbol and inspect provenance",
          "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success."
        ],
        "screen_recording_instructions": [
          "If your use is permitted, run the live command for one symbol. Inspect the last five available session bars. Capture retrieval time, source and actual date range. A closed market or holiday can reduce rows; do not invent current quotes.",
          "Inspect the result: A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "If your use is permitted, run the live command for one symbol. Inspect the last five available session bars. Capture retrieval time, source and actual date range. A closed market or holiday can reduce rows; do not invent current quotes.",
          "A nonempty live result is labeled yahoo-unadjusted, or a concrete access/network failure is retained without being called a success."
        ]
      },
      "step_id": "L05-S01",
      "lesson_id": "L05"
    },
    {
      "title": "Exercise an invalid bar",
      "purpose": "Empty live data is a failure to investigate, not proof the symbol has no history.",
      "user_action": "Copy prices.json to prices-bad.json and set one high below its close. Run the collector against a separate bad-prices.sqlite. Confirm it fails visibly. For a live error, record symbol, package version and status; use bounded retry/backoff and respect rate limits.",
      "explanation": "Empty live data is a failure to investigate, not proof the symbol has no history.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python finance_collector.py --fixture prices-bad.json --db bad-prices.sqlite",
        "macos": "python3 finance_collector.py --fixture prices-bad.json --db bad-prices.sqlite",
        "linux": "python3 finance_collector.py --fixture prices-bad.json --db bad-prices.sqlite"
      },
      "command_type": "shell",
      "required_inputs": [
        "finance_collector.py",
        "prices.json"
      ],
      "expected_result": "The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
      "resources": [
        "finance_collector.py",
        "prices.json"
      ],
      "checkpoint": {
        "what_is_being_checked": "Exercise an invalid bar",
        "success_condition": "The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
        "how_to_verify": "Record the invalid OHLC range produces an error and no successful FINANCE PASS receipt. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify exercise an invalid bar?",
          "answer": "The invalid OHLC range produces an error and no successful FINANCE PASS receipt. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use finance_collector.py, prices.json. Work in the same practice folder."
        }
      ],
      "quiz": {
        "question": "Can adjusted and unadjusted daily prices be mixed silently?",
        "answer_type": "single_choice",
        "choices": [
          "No; store adjustment policy and corporate actions explicitly.",
          "Yes; the dates make them equivalent."
        ],
        "correct_answer": 0,
        "explanation": "Splits and dividends can change comparability."
      },
      "coach": {
        "intro": "We are going to exercise an invalid bar. The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
        "demo": "Copy prices.json to prices-bad.json and set one high below its close. Run the collector against a separate bad-prices.sqlite. Confirm it fails visibly. For a live error, record symbol, package version and status; use bounded retry/backoff and respect rate limits.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate exercise an invalid bar",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Copy prices.json to prices-bad.json and set one high below its close. Run the collector against a separate bad-prices.sqlite. Confirm it fails visibly. For a live error, record symbol, package version and status; use bounded retry/backoff and respect rate limits. The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
        "on_screen_text": [
          "Exercise an invalid bar",
          "The invalid OHLC range produces an error and no successful FINANCE PASS receipt."
        ],
        "screen_recording_instructions": [
          "Copy prices.json to prices-bad.json and set one high below its close. Run the collector against a separate bad-prices.sqlite. Confirm it fails visibly. For a live error, record symbol, package version and status; use bounded retry/backoff and respect rate limits.",
          "Inspect the result: The invalid OHLC range produces an error and no successful FINANCE PASS receipt.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The invalid OHLC range produces an error and no successful FINANCE PASS receipt."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Copy prices.json to prices-bad.json and set one high below its close. Run the collector against a separate bad-prices.sqlite. Confirm it fails visibly. For a live error, record symbol, package version and status; use bounded retry/backoff and respect rate limits.",
          "The invalid OHLC range produces an error and no successful FINANCE PASS receipt."
        ]
      },
      "step_id": "L06-S01",
      "lesson_id": "L06"
    },
    {
      "title": "Repeat and document the final run",
      "purpose": "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
      "user_action": "Run the chosen fixture or approved live path twice. Verify stable row counts and source labels. Save the contract, version record, last successful receipt and one failure case. A scheduler is an optional later step requiring a bounded interval and failure alert.",
      "explanation": "Keep the input and the observed result together so you can reproduce this action later.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python finance_collector.py --fixture prices.json",
        "macos": "python3 finance_collector.py --fixture prices.json",
        "linux": "python3 finance_collector.py --fixture prices.json"
      },
      "command_type": "shell",
      "required_inputs": [
        "finance_collector.py",
        "data-dictionary.md"
      ],
      "expected_result": "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
      "resources": [
        "finance_collector.py",
        "data-dictionary.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Repeat and document the final run",
        "success_condition": "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
        "how_to_verify": "Record the collector has repeatable storage, correct provenance, visible failures and documented scope. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The collector has repeatable storage, correct provenance, visible failures and documented scope.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [
          "FINANCE PASS"
        ],
        "user_visible_success_message": "Evidence saved. The collector has repeatable storage, correct provenance, visible failures and documented scope.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify repeat and document the final run?",
          "answer": "The collector has repeatable storage, correct provenance, visible failures and documented scope. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use finance_collector.py, data-dictionary.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to repeat and document the final run. The collector has repeatable storage, correct provenance, visible failures and documented scope.",
        "demo": "Run the chosen fixture or approved live path twice. Verify stable row counts and source labels. Save the contract, version record, last successful receipt and one failure case. A scheduler is an optional later step requiring a bounded interval and failure alert.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate repeat and document the final run",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Run the chosen fixture or approved live path twice. Verify stable row counts and source labels. Save the contract, version record, last successful receipt and one failure case. A scheduler is an optional later step requiring a bounded interval and failure alert. The collector has repeatable storage, correct provenance, visible failures and documented scope.",
        "on_screen_text": [
          "Repeat and document the final run",
          "The collector has repeatable storage, correct provenance, visible failures and documented scope."
        ],
        "screen_recording_instructions": [
          "Run the chosen fixture or approved live path twice. Verify stable row counts and source labels. Save the contract, version record, last successful receipt and one failure case. A scheduler is an optional later step requiring a bounded interval and failure alert.",
          "Inspect the result: The collector has repeatable storage, correct provenance, visible failures and documented scope.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The collector has repeatable storage, correct provenance, visible failures and documented scope."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Run the chosen fixture or approved live path twice. Verify stable row counts and source labels. Save the contract, version record, last successful receipt and one failure case. A scheduler is an optional later step requiring a bounded interval and failure alert.",
          "The collector has repeatable storage, correct provenance, visible failures and documented scope."
        ]
      },
      "step_id": "L07-S01",
      "lesson_id": "L07"
    },
    {
      "title": "Write a repeatable onboarding checklist",
      "purpose": "The September 23 BuildBotsBetter profile wipe removed Desktop, Documents and hidden agent memory together. Repeatable onboarding protects the knowledge needed to recover.",
      "user_action": "Fill in onboarding-checklist.md for your agent. Record AGENTS.md, the tool’s user settings and memory folder, the assigned workspace, permissions, guard location, backup schedule, and a final proof task. Keep the checklist in your project.",
      "explanation": "The September 23 BuildBotsBetter profile wipe removed Desktop, Documents and hidden agent memory together. Repeatable onboarding protects the knowledge needed to recover.",
      "estimated_time": "6 min",
      "action_type": "inspect",
      "commands": {
        "all": ""
      },
      "command_type": "shell",
      "required_inputs": [
        "onboarding-checklist.md"
      ],
      "expected_result": "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
      "resources": [
        "onboarding-checklist.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Write a repeatable onboarding checklist",
        "success_condition": "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
        "how_to_verify": "Record the checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify write a repeatable onboarding checklist?",
          "answer": "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use onboarding-checklist.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to write a repeatable onboarding checklist. The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
        "demo": "Fill in onboarding-checklist.md for your agent. Record AGENTS.md, the tool’s user settings and memory folder, the assigned workspace, permissions, guard location, backup schedule, and a final proof task. Keep the checklist in your project.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate write a repeatable onboarding checklist",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Fill in onboarding-checklist.md for your agent. Record AGENTS.md, the tool’s user settings and memory folder, the assigned workspace, permissions, guard location, backup schedule, and a final proof task. Keep the checklist in your project. The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
        "on_screen_text": [
          "Write a repeatable onboarding checklist",
          "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification."
        ],
        "screen_recording_instructions": [
          "Fill in onboarding-checklist.md for your agent. Record AGENTS.md, the tool’s user settings and memory folder, the assigned workspace, permissions, guard location, backup schedule, and a final proof task. Keep the checklist in your project.",
          "Inspect the result: The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Fill in onboarding-checklist.md for your agent. Record AGENTS.md, the tool’s user settings and memory folder, the assigned workspace, permissions, guard location, backup schedule, and a final proof task. Keep the checklist in your project.",
          "The checklist contains a concrete path and owner for rules, memory, permissions, guard, backup, restore and final verification."
        ]
      },
      "step_id": "L08-S01",
      "lesson_id": "L08"
    },
    {
      "title": "Demonstrate the variable-path limit safely",
      "purpose": "A command-text hook can miss a target computed inside a script or variable. This demonstrator checks resolved paths but is not an operating-system sandbox. For a real operation, enforce the resolved boundary at the operation itself; symlinks and races still require care.",
      "user_action": "Run workspace_guard.py --self-test. Read the source: the target is resolved before deciding. The variable_target case points at the home folder but performs no filesystem operation. Compare this with a hook that sees only command text.",
      "explanation": "A command-text hook can miss a target computed inside a script or variable. This demonstrator checks resolved paths but is not an operating-system sandbox. For a real operation, enforce the resolved boundary at the operation itself; symlinks and races still require care.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python workspace_guard.py --self-test",
        "macos": "python3 workspace_guard.py --self-test",
        "linux": "python3 workspace_guard.py --self-test"
      },
      "command_type": "shell",
      "required_inputs": [
        "workspace_guard.py"
      ],
      "expected_result": "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
      "resources": [
        "workspace_guard.py"
      ],
      "checkpoint": {
        "what_is_being_checked": "Demonstrate the variable-path limit safely",
        "success_condition": "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
        "how_to_verify": "Record gUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
          "I can repeat this action from the saved input."
        ],
        "tokens": [
          "GUARD PASS"
        ],
        "user_visible_success_message": "Evidence saved. GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify demonstrate the variable-path limit safely?",
          "answer": "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use workspace_guard.py. Work in the same practice folder."
        }
      ],
      "quiz": {
        "question": "Does a command-text hook guarantee safety for a path computed inside a script?",
        "answer_type": "single_choice",
        "choices": [
          "No; add enforcement at the resolved operation boundary and independent recovery.",
          "Yes, because the command looks harmless."
        ],
        "correct_answer": 0,
        "explanation": "The profile-wipe failure can involve a runtime variable whose value the text hook cannot see."
      },
      "coach": {
        "intro": "We are going to demonstrate the variable-path limit safely. GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
        "demo": "Run workspace_guard.py --self-test. Read the source: the target is resolved before deciding. The variable_target case points at the home folder but performs no filesystem operation. Compare this with a hook that sees only command text.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate demonstrate the variable-path limit safely",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Run workspace_guard.py --self-test. Read the source: the target is resolved before deciding. The variable_target case points at the home folder but performs no filesystem operation. Compare this with a hook that sees only command text. GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
        "on_screen_text": [
          "Demonstrate the variable-path limit safely",
          "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed."
        ],
        "screen_recording_instructions": [
          "Run workspace_guard.py --self-test. Read the source: the target is resolved before deciding. The variable_target case points at the home folder but performs no filesystem operation. Compare this with a hook that sees only command text.",
          "Inspect the result: GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Run workspace_guard.py --self-test. Read the source: the target is resolved before deciding. The variable_target case points at the home folder but performs no filesystem operation. Compare this with a hook that sees only command text.",
          "GUARD PASS reports inside allowed and profile, outside, variable-derived profile and workspace root denied; no deletion was executed."
        ]
      },
      "step_id": "L08-S02",
      "lesson_id": "L08"
    },
    {
      "title": "Verify the actual protection in your tool",
      "purpose": "A broken hook that blocks everything can look like protection. Some tools fail open when hooks fail. Codex hook changes need review/trust; Grok Build needs its own deny protocol; Antigravity uses a different JSON protocol. Never treat a prompt rule or an inactive hook as enforcement.",
      "user_action": "For CLI tools, open the hook/permissions screen and confirm the configured guard is active. Use your tool’s documented pre-command hook protocol; the BBB working reference is linked in Sources. Run a harmless directory listing, then a guard dry-run targeting the profile. Do not execute a destructive profile probe. Grok Bot has no proven local shell guard here: use project-only tasks and reviewed actions, with backups.",
      "explanation": "A broken hook that blocks everything can look like protection. Some tools fail open when hooks fail. Codex hook changes need review/trust; Grok Build needs its own deny protocol; Antigravity uses a different JSON protocol. Never treat a prompt rule or an inactive hook as enforcement.",
      "estimated_time": "6 min",
      "action_type": "inspect",
      "commands": {
        "all": ""
      },
      "command_type": "shell",
      "required_inputs": [
        "workspace_guard.py",
        "onboarding-checklist.md"
      ],
      "expected_result": "A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
      "resources": [
        "workspace_guard.py",
        "onboarding-checklist.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Verify the actual protection in your tool",
        "success_condition": "A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
        "how_to_verify": "Record a harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The harmless command succeeds.",
          "The boundary dry-run denies a profile target.",
          "I recorded the tool’s active hook state, or explicitly recorded that this tool has no working local guard."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I install a guard for this tool?",
          "answer": "Use the linked BBB safety reference for the exact tool/version protocol. Merge into the existing hooks instead of overwriting settings. Review/trust the hook if required, then verify a harmless call and a denied dry-run. The workspace_guard.py file is a teaching demonstration, not a universal hook adapter."
        },
        {
          "question": "Does Grok Bot have a working local delete guard?",
          "answer": "The project’s live September 29 tests found no working shell hook. Restrict the tasks and workspace you hand it, keep independent backups, and do not claim local deletion is guarded."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to verify the actual protection in your tool. A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
        "demo": "For CLI tools, open the hook/permissions screen and confirm the configured guard is active. Use your tool’s documented pre-command hook protocol; the BBB working reference is linked in Sources. Run a harmless directory listing, then a guard dry-run targeting the profile. Do not execute a destructive profile probe. Grok Bot has no proven local shell guard here: use project-only tasks and reviewed actions, with backups.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate verify the actual protection in your tool",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "For CLI tools, open the hook/permissions screen and confirm the configured guard is active. Use your tool’s documented pre-command hook protocol; the BBB working reference is linked in Sources. Run a harmless directory listing, then a guard dry-run targeting the profile. Do not execute a destructive profile probe. Grok Bot has no proven local shell guard here: use project-only tasks and reviewed actions, with backups. A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
        "on_screen_text": [
          "Verify the actual protection in your tool",
          "A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation."
        ],
        "screen_recording_instructions": [
          "For CLI tools, open the hook/permissions screen and confirm the configured guard is active. Use your tool’s documented pre-command hook protocol; the BBB working reference is linked in Sources. Run a harmless directory listing, then a guard dry-run targeting the profile. Do not execute a destructive profile probe. Grok Bot has no proven local shell guard here: use project-only tasks and reviewed actions, with backups.",
          "Inspect the result: A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "For CLI tools, open the hook/permissions screen and confirm the configured guard is active. Use your tool’s documented pre-command hook protocol; the BBB working reference is linked in Sources. Run a harmless directory listing, then a guard dry-run targeting the profile. Do not execute a destructive profile probe. Grok Bot has no proven local shell guard here: use project-only tasks and reviewed actions, with backups.",
          "A harmless command runs, the guard dry-run returns DENY, and the checklist records the actual hook protocol and active state or the Grok Bot limitation."
        ]
      },
      "step_id": "L08-S03",
      "lesson_id": "L08"
    },
    {
      "title": "Enable a real backup of memory and project files",
      "purpose": "System Restore alone is not a personal-file backup. Previous Versions can disappear as shadow storage fills; OneDrive’s common-folder backup omits hidden agent folders.",
      "user_action": "Connect a second backup drive. Windows: configure System Protection as additional recovery and use a scheduled copy/File History that explicitly includes hidden agent folders. macOS: configure Time Machine and verify dot folders are included. Linux: use a home backup such as restic/Deja Dup; Timeshift omits /home by default. Download the copy-only profile backup script for your platform, inspect it, and adapt the folder list to your tool. Record the last successful scheduled run; protect backup access because it may contain credentials.",
      "explanation": "System Restore alone is not a personal-file backup. Previous Versions can disappear as shadow storage fills; OneDrive’s common-folder backup omits hidden agent folders.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": ".\\profile-backup.ps1 -Destination D:\\Backups\\llm-profiles",
        "macos": "bash profile-backup.sh /Volumes/YourBackup/llm-profiles",
        "linux": "bash profile-backup.sh /media/YourBackup/llm-profiles"
      },
      "command_type": "shell",
      "required_inputs": [
        "profile-backup.ps1",
        "profile-backup.sh",
        "onboarding-checklist.md"
      ],
      "expected_result": "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
      "resources": [
        "profile-backup.ps1",
        "profile-backup.sh",
        "onboarding-checklist.md"
      ],
      "checkpoint": {
        "what_is_being_checked": "Enable a real backup of memory and project files",
        "success_condition": "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
        "how_to_verify": "Record a backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The destination is a mounted second drive.",
          "The hidden memory/settings folders and project files are included.",
          "An automated backup is enabled and its latest successful run is recorded."
        ],
        "tokens": [],
        "user_visible_success_message": "Evidence saved. A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The backup drive is missing or the script reports a failure",
          "likely_cause": "The destination may be on the same volume, unmounted, or unwritable.",
          "diagnostic_question": "Can you create a scratch file on the actual second drive?",
          "fix": "Mount the drive and choose an accessible backup directory. Inspect every error; robocopy codes 8 and higher are failures.",
          "alternative_fix": "Use the operating system backup application and verify the same folder coverage and successful run.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Mount the drive and choose an accessible backup directory. Inspect every error; robocopy codes 8 and higher are failures."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify enable a real backup of memory and project files?",
          "answer": "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use profile-backup.ps1, profile-backup.sh, onboarding-checklist.md. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to enable a real backup of memory and project files. A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
        "demo": "Connect a second backup drive. Windows: configure System Protection as additional recovery and use a scheduled copy/File History that explicitly includes hidden agent folders. macOS: configure Time Machine and verify dot folders are included. Linux: use a home backup such as restic/Deja Dup; Timeshift omits /home by default. Download the copy-only profile backup script for your platform, inspect it, and adapt the folder list to your tool. Record the last successful scheduled run; protect backup access because it may contain credentials.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Mount the drive and choose an accessible backup directory. Inspect every error; robocopy codes 8 and higher are failures.",
        "help": "Can you create a scratch file on the actual second drive?"
      },
      "video": {
        "purpose": "Demonstrate enable a real backup of memory and project files",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Connect a second backup drive. Windows: configure System Protection as additional recovery and use a scheduled copy/File History that explicitly includes hidden agent folders. macOS: configure Time Machine and verify dot folders are included. Linux: use a home backup such as restic/Deja Dup; Timeshift omits /home by default. Download the copy-only profile backup script for your platform, inspect it, and adapt the folder list to your tool. Record the last successful scheduled run; protect backup access because it may contain credentials. A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
        "on_screen_text": [
          "Enable a real backup of memory and project files",
          "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded."
        ],
        "screen_recording_instructions": [
          "Connect a second backup drive. Windows: configure System Protection as additional recovery and use a scheduled copy/File History that explicitly includes hidden agent folders. macOS: configure Time Machine and verify dot folders are included. Linux: use a home backup such as restic/Deja Dup; Timeshift omits /home by default. Download the copy-only profile backup script for your platform, inspect it, and adapt the folder list to your tool. Record the last successful scheduled run; protect backup access because it may contain credentials.",
          "Inspect the result: A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Connect a second backup drive. Windows: configure System Protection as additional recovery and use a scheduled copy/File History that explicitly includes hidden agent folders. macOS: configure Time Machine and verify dot folders are included. Linux: use a home backup such as restic/Deja Dup; Timeshift omits /home by default. Download the copy-only profile backup script for your platform, inspect it, and adapt the folder list to your tool. Record the last successful scheduled run; protect backup access because it may contain credentials.",
          "A backup on another drive includes the tool’s user settings and memory folder and this project, and a successful schedule/time is recorded."
        ]
      },
      "step_id": "L08-S04",
      "lesson_id": "L08"
    },
    {
      "title": "Practice a hash-verified restore",
      "purpose": "A backup becomes useful only when restoration has been practiced. A same-volume practice copy proves the procedure but not protection against disk failure.",
      "user_action": "Run restore_drill.py with a separate backup directory. The script creates a new proof file, copies it, restores a second copy, and compares SHA256 hashes. Then restore one non-secret file from your actual agent memory backup into a separate scratch directory and open it; do not overwrite the live profile.",
      "explanation": "A backup becomes useful only when restoration has been practiced. A same-volume practice copy proves the procedure but not protection against disk failure.",
      "estimated_time": "6 min",
      "action_type": "command",
      "commands": {
        "windows": "python restore_drill.py --backup-root D:\\Backups\\bbb-practice --work-root practice",
        "macos": "python3 restore_drill.py --backup-root /Volumes/YourBackup/bbb-practice --work-root practice",
        "linux": "python3 restore_drill.py --backup-root /media/YourBackup/bbb-practice --work-root practice"
      },
      "command_type": "shell",
      "required_inputs": [
        "restore_drill.py"
      ],
      "expected_result": "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
      "resources": [
        "restore_drill.py"
      ],
      "checkpoint": {
        "what_is_being_checked": "Practice a hash-verified restore",
        "success_condition": "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
        "how_to_verify": "Record rESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch. Include the actual result or a specific observation; do not paste credentials.",
        "criteria": [
          "The proof file SHA256 hashes match.",
          "I restored and opened a non-secret memory/settings file from my real backup.",
          "The restored file is in scratch; the live profile was not overwritten."
        ],
        "tokens": [
          "RESTORE PASS"
        ],
        "user_visible_success_message": "Evidence saved. RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
        "failure_message": "Compare the observed output with the required result before continuing.",
        "troubleshooting_path": "Open the help for this step."
      },
      "troubleshooting": [
        {
          "problem": "The result differs from the checkpoint",
          "likely_cause": "You may be in a different folder or using a different input/version.",
          "diagnostic_question": "What is the current directory, exact command, exit code and complete output?",
          "fix": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
          "alternative_fix": "Open the supplied resource and inspect the input manually; use the expected-result example to narrow the difference.",
          "when_to_escalate": "Stop after two explained attempts if the problem needs account access, permissions or changes outside this workspace. Share redacted evidence.",
          "bot_coach_response": "Compare the input filename and working directory with this step. Rerun only after correcting that difference."
        }
      ],
      "faqs": [
        {
          "question": "How do I verify practice a hash-verified restore?",
          "answer": "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch. Keep the command or observation with your evidence."
        },
        {
          "question": "Which files do I need for this step?",
          "answer": "Use restore_drill.py. Work in the same practice folder."
        }
      ],
      "quiz": null,
      "coach": {
        "intro": "We are going to practice a hash-verified restore. RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
        "demo": "Run restore_drill.py with a separate backup directory. The script creates a new proof file, copies it, restores a second copy, and compares SHA256 hashes. Then restore one non-secret file from your actual agent memory backup into a separate scratch directory and open it; do not overwrite the live profile.",
        "handoff": "Try this in your own practice workspace, then compare the result.",
        "success": "Keep that result with your evidence.",
        "failure": "Compare the input filename and working directory with this step. Rerun only after correcting that difference.",
        "help": "What is the current directory, exact command, exit code and complete output?"
      },
      "video": {
        "purpose": "Demonstrate practice a hash-verified restore",
        "duration_target": "45–75 seconds",
        "visual_type": "step walkthrough with optional browser narration; no rendered video is claimed",
        "narration_script": "Run restore_drill.py with a separate backup directory. The script creates a new proof file, copies it, restores a second copy, and compares SHA256 hashes. Then restore one non-secret file from your actual agent memory backup into a separate scratch directory and open it; do not overwrite the live profile. RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
        "on_screen_text": [
          "Practice a hash-verified restore",
          "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch."
        ],
        "screen_recording_instructions": [
          "Run restore_drill.py with a separate backup directory. The script creates a new proof file, copies it, restores a second copy, and compares SHA256 hashes. Then restore one non-secret file from your actual agent memory backup into a separate scratch directory and open it; do not overwrite the live profile.",
          "Inspect the result: RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch.",
          "Record the evidence and check each criterion."
        ],
        "animation_instructions": "Highlight the action, then the corresponding result; avoid motion during command copying.",
        "cursor_instructions": "Point to the exact input and checkpoint; do not hide errors.",
        "important_visuals": [
          "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch."
        ],
        "bot_position": "right sidebar",
        "bot_expression": "calm",
        "transition": "Continue after checkpoint",
        "captions": [
          "Run restore_drill.py with a separate backup directory. The script creates a new proof file, copies it, restores a second copy, and compares SHA256 hashes. Then restore one non-secret file from your actual agent memory backup into a separate scratch directory and open it; do not overwrite the live profile.",
          "RESTORE PASS contains matching hashes; the actual memory file is readable after restoration into scratch."
        ]
      },
      "step_id": "L08-S05",
      "lesson_id": "L08"
    }
  ],
  "resources": [
    {
      "resource_id": "R001",
      "name": "workspace_guard.py",
      "type": "py",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# VERSION HISTORY\n# 2026-10-05 EDT | chatgpt_codex | overnight-catalog | v1: learner resource.\n\"\"\"Dry-run resolved-path boundary demonstration. This script never deletes anything.\"\"\"\nimport argparse\nfrom pathlib import Path\n\ndef permitted(target, workspace):\n    root = Path(workspace).resolve()\n    candidate = Path(target).resolve()\n    home = Path.home().resolve()\n    if root == home or root == root.anchor or root in home.parents:\n        return False\n    return candidate != root and root in candidate.parents and candidate != home and candidate not in home.parents\n\ndef main():\n    p=argparse.ArgumentParser(description=__doc__)\n    p.add_argument('--workspace',default='practice')\n    p.add_argument('--target')\n    p.add_argument('--self-test',action='store_true')\n    a=p.parse_args()\n    root=Path(a.workspace).resolve()\n    if a.self_test:\n        assert permitted(root/'proof.txt',root)\n        assert not permitted(Path.home(),root)\n        assert not permitted(root.parent/'outside.txt',root)\n        assert not permitted(root,root)\n        variable_target=Path.home()\n        assert not permitted(variable_target,root)\n        print('GUARD PASS: inside allowed; profile, variable-derived profile, outside, workspace root denied; no deletion executed')\n    else:\n        if not a.target:p.error('--target required')\n        allowed=permitted(a.target,a.workspace)\n        print(('ALLOW' if allowed else 'DENY')+': resolved boundary; dry-run only')\n        raise SystemExit(0 if allowed else 2)\nif __name__=='__main__':main()\n",
      "filename": "workspace_guard.py",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R002",
      "name": "restore_drill.py",
      "type": "py",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# VERSION HISTORY\n# 2026-10-05 EDT | chatgpt_codex | overnight-catalog | v1: learner resource.\n\"\"\"Backup and restore a new proof file only; never edits an existing file or profile.\"\"\"\nimport argparse,hashlib,json,logging\nfrom datetime import datetime,timezone\nfrom pathlib import Path\nimport shutil\ndef digest(p):return hashlib.sha256(p.read_bytes()).hexdigest()\ndef main():\n    a=argparse.ArgumentParser(description=__doc__)\n    a.add_argument('--backup-root',required=True)\n    a.add_argument('--work-root',default='practice')\n    x=a.parse_args()\n    run=datetime.now(timezone.utc).strftime('%Y%m%dT%H%M%S%fZ')\n    work=Path(x.work_root).resolve()/('restore-'+run)\n    backup=Path(x.backup_root).resolve()/('restore-'+run)\n    if work==backup or work in backup.parents or backup in work.parents:raise SystemExit('Use separate, non-overlapping work and backup roots')\n    work.mkdir(parents=True,exist_ok=False);backup.mkdir(parents=True,exist_ok=False)\n    logging.basicConfig(filename=work/'drill.log',encoding='utf-8',level=logging.INFO)\n    source=work/'proof.txt';source.write_text('BuildBotsBetter restore proof '+run,encoding='utf-8')\n    shutil.copy2(source,backup/'proof.txt')\n    restored=work/'restored.txt';shutil.copy2(backup/'proof.txt',restored)\n    assert digest(source)==digest(restored)\n    receipt={'result':'RESTORE PASS','source_sha256':digest(source),'restored_sha256':digest(restored),'backup_root':str(backup),'off_volume':work.anchor.lower()!=backup.anchor.lower(),'scope':'new proof file only; does not establish a scheduled profile backup'}\n    (work/'receipt.json').write_text(json.dumps(receipt,indent=2),encoding='utf-8')\n    logging.info('Proof backup and hash-verified restore completed')\n    print(json.dumps(receipt,indent=2))\n    if not receipt['off_volume']:print('SAME VOLUME: practice passed; configure a second drive for disaster recovery')\nif __name__=='__main__':main()\n",
      "filename": "restore_drill.py",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R003",
      "name": "onboarding-checklist.md",
      "type": "md",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# Repeatable agent onboarding\nagent:\ntool version:\nrules file:\nmemory/settings location:\nassigned workspace:\npermissions / actions needing approval:\nhook location and protocol:\nguard active (harmless command + denied dry-run):\nvariable-derived path limit understood:\nbackup destination (second drive):\nbackup schedule / last successful run:\nrestored memory file / matching SHA256:\nfinal task / evidence / reviewer:\n\nProtect memory/settings and project files. A prompt rule is not an operating-system boundary.\nA command-text hook can miss a path computed in a script or variable. Resolve paths at the\noperation boundary and fail closed; keep independent backups and monitoring.\nWindows System Restore reverts system components, not a reliable personal-file backup.\nOneDrive folder backup does not automatically include hidden agent folders.\nmacOS: check Time Machine includes hidden agent folders. Linux: Timeshift excludes /home by\ndefault; use a separate home backup or explicitly include it.\n",
      "filename": "onboarding-checklist.md",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R004",
      "name": "profile-backup.ps1",
      "type": "ps1",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# VERSION HISTORY\n# 2026-10-05 EDT | chatgpt_codex | overnight-catalog | v1: copy-only explicit profile backup.\nparam([Parameter(Mandatory=$true)][string]$Destination,[string]$ProjectPath=(Get-Location).Path)\n$ErrorActionPreference='Stop'\n$destRoot=[IO.Path]::GetFullPath($Destination)\n$profileRoot=[IO.Path]::GetFullPath($env:USERPROFILE)\nif ([IO.Path]::GetPathRoot($destRoot) -eq [IO.Path]::GetPathRoot($profileRoot)) { throw 'Choose a backup destination on a second drive.' }\nif (-not (Test-Path -LiteralPath ([IO.Path]::GetPathRoot($destRoot)))) { throw 'Backup drive is unavailable.' }\n$runDir=Join-Path $destRoot (Get-Date -Format 'yyyyMMdd-HHmmss-fff')\nNew-Item -ItemType Directory -Path $runDir -ErrorAction Stop | Out-Null\nforeach ($folderName in @('.codex','.claude','.grok','.qwen','.gemini')) {\n  $sourceDir=Join-Path $profileRoot $folderName\n  if (Test-Path -LiteralPath $sourceDir) {\n    $copyDir=Join-Path $runDir $folderName\n    & robocopy $sourceDir $copyDir /E /XJ /R:1 /W:1 /COPY:DAT /DCOPY:DAT /NP\n    if ($LASTEXITCODE -ge 8) { throw \"Backup failed for $folderName (robocopy $LASTEXITCODE).\" }\n  }\n}\n$projectSource=[IO.Path]::GetFullPath($ProjectPath)\nif (-not (Test-Path -LiteralPath $projectSource -PathType Container)) { throw 'Project directory is unavailable.' }\n& robocopy $projectSource (Join-Path $runDir 'project') /E /XJ /R:1 /W:1 /COPY:DAT /DCOPY:DAT /NP\nif ($LASTEXITCODE -ge 8) { throw \"Project backup failed (robocopy $LASTEXITCODE).\" }\n\"PROFILE BACKUP PASS: $runDir\"\n# Copy-only: no /MIR, /PURGE or deletion. Backup may contain credentials; protect the drive.\n# Add the Grok Bot profile and project path explicitly after finding them in your own installation.\n",
      "filename": "profile-backup.ps1",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R005",
      "name": "profile-backup.sh",
      "type": "sh",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "#!/usr/bin/env bash\n# VERSION HISTORY\n# 2026-10-05 EDT | chatgpt_codex | overnight-catalog | v1: copy-only explicit profile backup.\nset -euo pipefail\ndest=${1:?Pass a mounted external-drive backup directory}\nproject=${2:-$PWD}\nmkdir -p \"$dest\"\nif [ \"$(df -P \"$HOME\" | tail -1 | awk '{print $1}')\" = \"$(df -P \"$dest\" | tail -1 | awk '{print $1}')\" ]; then\n  echo 'Choose a destination on another mounted filesystem.' >&2; exit 2\nfi\nrun=\"$dest/$(date -u +%Y%m%dT%H%M%SZ)-$$\"\nmkdir \"$run\"\nfor name in .codex .claude .grok .qwen .gemini; do\n  if [ -d \"$HOME/$name\" ]; then cp -pR \"$HOME/$name\" \"$run/$name\"; fi\ndone\nif [ ! -d \"$project\" ]; then echo 'Project directory is unavailable.' >&2; exit 2; fi\ncp -pR \"$project\" \"$run/project\"\necho \"PROFILE BACKUP PASS: $run\"\n# This backup can contain credentials; protect access to the backup drive.\n",
      "filename": "profile-backup.sh",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R006",
      "name": "prices.json",
      "type": "json",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "[\n  {\n    \"symbol\": \"DEMO\",\n    \"date\": \"2026-10-01\",\n    \"open\": 100,\n    \"high\": 104,\n    \"low\": 99,\n    \"close\": 102,\n    \"volume\": 1000\n  },\n  {\n    \"symbol\": \"DEMO\",\n    \"date\": \"2026-10-02\",\n    \"open\": 102,\n    \"high\": 105,\n    \"low\": 101,\n    \"close\": 104,\n    \"volume\": 1500\n  }\n]",
      "filename": "prices.json",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R007",
      "name": "finance_collector.py",
      "type": "py",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# VERSION HISTORY\n# 2026-10-05 EDT | chatgpt_codex | overnight-catalog | v1: learner resource.\n\"\"\"Educational price collector. Offline fixture or optional yfinance live download.\"\"\"\nimport argparse,json,sqlite3,math,logging\nfrom pathlib import Path\nfrom datetime import datetime,timezone\ndef store(rows,db_path,source):\n    db=sqlite3.connect(db_path)\n    db.execute('CREATE TABLE IF NOT EXISTS prices(symbol TEXT,date TEXT,open REAL,high REAL,low REAL,close REAL,volume INTEGER,source TEXT,retrieved_utc TEXT,PRIMARY KEY(symbol,date,source))')\n    stamp=datetime.now(timezone.utc).isoformat();written=0\n    with db:\n        for r in rows:\n            values=[float(r[k]) for k in ('open','high','low','close')]\n            if not all(math.isfinite(v) and v>0 for v in values) or int(r['volume'])<0:raise ValueError('invalid price/volume')\n            if values[1]<max(values[0],values[2],values[3]) or values[2]>min(values[0],values[1],values[3]):raise ValueError('invalid OHLC range')\n            datetime.strptime(r['date'],'%Y-%m-%d')\n            if not str(r['symbol']).strip():raise ValueError('missing symbol')\n            db.execute('INSERT INTO prices VALUES (?,?,?,?,?,?,?,?,?) ON CONFLICT(symbol,date,source) DO UPDATE SET open=excluded.open,high=excluded.high,low=excluded.low,close=excluded.close,volume=excluded.volume,retrieved_utc=excluded.retrieved_utc',(r['symbol'],r['date'],*values,int(r['volume']),source,stamp));written+=1\n    total=db.execute('SELECT count(*) FROM prices').fetchone()[0];db.close();return written,total\ndef live(symbol):\n    import yfinance as yf\n    frame=yf.Ticker(symbol).history(period='5d',auto_adjust=False,actions=True)\n    if frame.empty:raise ValueError('No rows returned; symbol/rate limit/network must be investigated')\n    return [dict(symbol=symbol,date=index.strftime('%Y-%m-%d'),open=row['Open'],high=row['High'],low=row['Low'],close=row['Close'],volume=int(row['Volume'])) for index,row in frame.iterrows()]\ndef main():\n    p=argparse.ArgumentParser(description=__doc__);g=p.add_mutually_exclusive_group(required=True);g.add_argument('--fixture');g.add_argument('--live');p.add_argument('--db',default='prices.sqlite');a=p.parse_args()\n    Path('logs').mkdir(exist_ok=True);logging.basicConfig(filename='logs/finance.log',encoding='utf-8',level=logging.INFO)\n    rows=live(a.live) if a.live else json.loads(Path(a.fixture).read_text(encoding='utf-8'));source='yahoo-unadjusted' if a.live else 'synthetic-fixture'\n    written,total=store(rows,a.db,source);logging.info('written=%d total=%d source=%s',written,total,source);print(f'FINANCE PASS: written={written} total={total} source={source}')\nif __name__=='__main__':main()\n",
      "filename": "finance_collector.py",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R008",
      "name": "requirements-live.txt",
      "type": "txt",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "yfinance\n",
      "filename": "requirements-live.txt",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    },
    {
      "resource_id": "R009",
      "name": "data-dictionary.md",
      "type": "md",
      "purpose": "Working resource used by this Build; inspect before running.",
      "contents": "# Price data contract\nsymbol: exact provider symbol; date: exchange session date, not UTC midnight.\nOHLC: unadjusted in this collector. Adj Close and actions need separate columns for analysis.\nvolume: provider-reported count; source and retrieved_utc: provenance.\nNever combine adjusted and unadjusted series silently. Quotes may be delayed or corrected.\nDEMO fixtures are synthetic, not market data. Educational collection is not trading guidance.\n",
      "filename": "data-dictionary.md",
      "generated_from": "BUILD_SPEC.json.resources",
      "version": "2.0"
    }
  ],
  "bot_coach": {
    "bot_name": "Buzz",
    "bot_role": "Offline reviewed step coach",
    "personality": "patient and concrete",
    "tone": "plain",
    "teaching_style": "hint, diagnostic, action, checkpoint",
    "introduction": "Ask about the current step. I use reviewed local answers and queue unknown questions for review.",
    "encouragement_style": "Focus on observed results.",
    "troubleshooting_style": "Ask for the smallest reproducible evidence.",
    "limits": "This offline coach does not call an LLM or inspect your computer. Unknown questions enter a local exportable review queue, not a shared SQL FAQ."
  },
  "coach_interaction_model": {
    "stuck": "current diagnostic and first repair",
    "meaning": "current explanation",
    "error": "current troubleshooting",
    "why": "purpose",
    "skip": "require equivalent evidence",
    "alternative": "documented alternative",
    "finished": "record actual output",
    "start_over": "export then reset only this Build",
    "progressive_assistance": [
      "hint",
      "diagnostic",
      "walkthrough",
      "resource solution"
    ]
  },
  "website_specification": {
    "layout": "Lesson outline, actionable step, current-context coach",
    "features": [
      "platform selectors",
      "command copy with selection fallback",
      "evidence checklist",
      "practical quiz",
      "downloadable resource ZIP",
      "local progress",
      "evidence export",
      "unknown-question review queue"
    ],
    "checkpoint_model": "Learner supplies observations/output; tokens check expected shape only, not host truth.",
    "navigation": "Browse freely; checked next-button progression retains evidence.",
    "video": "spec-driven walkthrough and optional speech; full rendered media is a downstream production task."
  },
  "final_test": {
    "test_name": "Repeat the core workflow and restore its evidence",
    "instructions": "Repeat the last product-specific checkpoint from a fresh practice input, preserve actual output, then complete the Build Bot Better guard and restore checks. Export the evidence.",
    "required_inputs": [
      "workspace_guard.py",
      "restore_drill.py",
      "onboarding-checklist.md",
      "prices.json",
      "finance_collector.py",
      "data-dictionary.md"
    ],
    "success_conditions": [
      "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
      "Core output can be reproduced",
      "Guard limit explained",
      "Backup and restoration evidence retained"
    ],
    "automated_tests": "catalog_check.py records browser behavior and executable resources, with explicit scope.",
    "manual_tests": [
      "Review actual account sign-in where needed",
      "Check source/data assumptions",
      "Restore one real non-secret memory file"
    ],
    "expected_output": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "failure_paths": "Use the specific step diagnostic, retain failure evidence and stop when access is required."
  },
  "extensions": [
    {
      "title": "Use your own input",
      "action": "Replace the sample with one permitted real input and rerun the same checks."
    },
    {
      "title": "Add one failure case",
      "action": "Create a malformed or missing input; prove the workflow fails visibly and recovers."
    },
    {
      "title": "Automate after review",
      "action": "Write a bounded schedule with logging and a stop condition; obtain approval for external actions separately."
    }
  ],
  "metadata": {
    "SEO_title": "Yahoo Finance Data Collector | BuildBotsBetter",
    "SEO_description": "An educational OHLCV collector with synthetic offline practice, optional yfinance live retrieval, input validation, source-aware SQLite upserts and reproducible diagnostics.",
    "SEO_keywords": [
      "yahoo-finance-collector",
      "guided build",
      "verified outcome"
    ],
    "difficulty": "beginner",
    "related_builds": [
      "dogfooding",
      "buildbotsbetter-onboarding"
    ],
    "next_recommended_build": "dogfooding"
  },
  "automation_map": [
    {
      "output": "website",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "walkthrough",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "bot dialogue",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "resources",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "quiz",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "captions",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    },
    {
      "output": "metadata",
      "generated_from": "BUILD_SPEC.json",
      "human_review_required": true
    }
  ],
  "quality_assurance_report": {
    "scope": "Original instructional content, reviewed against shared brief; execution and browser receipts are stored under logs/catalog-acceptance.",
    "known_limits": [
      "Live Yahoo retrieval can fail due to access/rate limits and is not inferred from a fixture pass.",
      "This educational collector does not implement trading signals or recommendations."
    ]
  },
  "sources": [
    {
      "title": "yfinance project and usage notice",
      "url": "https://github.com/ranaroussi/yfinance"
    },
    {
      "title": "Python SQLite parameterized operations",
      "url": "https://docs.python.org/3/library/sqlite3.html"
    }
  ],
  "known_uncertainties": [
    "Live Yahoo retrieval can fail due to access/rate limits and is not inferred from a fixture pass.",
    "This educational collector does not implement trading signals or recommendations."
  ]
}
