# yt-fts - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `NotJoeMartinez/yt-fts` - capability: YouTube Full Text Search - Search all of YouTube from the command line - expected_user_outcome: YouTube Full Text Search - Search all of YouTube from the command line ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Project Overview and Architecture**: importance `high` - source_paths: README.md, CHANGELOG.md, src/yt_fts/yt_fts.py, src/yt_fts/config.py, src/yt_fts/db_utils.py - **Download, Ingestion, and Channel Management**: importance `high` - source_paths: src/yt_fts/download/download_handler.py, src/yt_fts/download/__init__.py, src/yt_fts/utils.py, docs/TROUBLESHOOTING_403.md, src/yt_fts/list.py - **Full Text and Semantic Search**: importance `high` - source_paths: src/yt_fts/search.py, src/yt_fts/export.py, src/yt_fts/utils.py, src/yt_fts/list.py, CHANGELOG.md - **AI Features: Embeddings, RAG Chat, and Summarization**: importance `high` - source_paths: src/yt_fts/llm/get_embeddings.py, src/yt_fts/llm/chatbot.py, src/yt_fts/llm/summarize.py, src/yt_fts/llm/__init__.py, src/yt_fts/config.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `7fbc0088f30672b6fbfe2ea7351fa42bafe1f886` - inspected_files: `README.md`, `pyproject.toml`, `docs/TROUBLESHOOTING_403.md`, `src/yt_fts/__init__.py`, `src/yt_fts/config.py`, `src/yt_fts/db_utils.py`, `src/yt_fts/download/__init__.py`, `src/yt_fts/download/download_handler.py`, `src/yt_fts/export.py`, `src/yt_fts/list.py`, `src/yt_fts/llm/__init__.py`, `src/yt_fts/llm/chatbot.py`, `src/yt_fts/llm/get_embeddings.py`, `src/yt_fts/llm/summarize.py`, `src/yt_fts/search.py`, `src/yt_fts/utils.py`, `src/yt_fts/yt_fts.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/138 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/180 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/183 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Installation risk requires verification - Trigger: Project evidence flags a installation risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/192 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Configuration risk requires verification - Trigger: Project evidence flags a configuration risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/184 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/NotJoeMartinez/yt-fts - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Runtime risk requires verification - Trigger: Project evidence flags a runtime risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/182 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Runtime risk requires verification - Trigger: Project evidence flags a runtime risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/189 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/NotJoeMartinez/yt-fts/issues/181 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/NotJoeMartinez/yt-fts - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.