# tinysearch - 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: `tinysearch/tinysearch` - capability: 🔍 Tiny, full-text search engine for static websites built with Rust and Wasm - expected_user_outcome: 🔍 Tiny, full-text search engine for static websites built with Rust and Wasm ## 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. - **Overview and Architecture**: importance `high` - source_paths: README.md, src/lib.rs, src/api.rs, src/bin/tinysearch.rs, src/bin/utils/mod.rs - **Configuration with tinysearch.toml**: importance `high` - source_paths: tinysearch.toml, examples/tinysearch.toml, examples/blog/tinysearch.toml, examples/ecommerce/tinysearch.toml, examples/documentation/tinysearch.toml - **Static Site Generator Integration**: importance `high` - source_paths: examples/README.md, examples/zola/README.md, examples/hugo/README.md, examples/pelican/README.md, examples/blog/README.md - **Rust Library API and Programmatic Usage**: importance `high` - source_paths: src/lib.rs, src/api.rs, examples/library_basic/main.rs, examples/library_advanced/main.rs, examples/search_index_type.rs ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `846b11480b8a438e6591c61f1483d36db0a38f1e` - inspected_files: `Dockerfile`, `README.md`, `examples/README.md`, `examples/blog/README.md`, `examples/blog/posts.json`, `examples/blog/tinysearch.toml`, `examples/documentation/README.md`, `examples/documentation/docs.json`, `examples/documentation/tinysearch.toml`, `examples/ecommerce/README.md`, `examples/ecommerce/products.json`, `examples/ecommerce/tinysearch.toml`, `examples/hugo/README.md`, `examples/index.json`, `examples/pelican/README.md`, `examples/tinysearch.toml`, `examples/yew-example-crate/Cargo.toml`, `examples/yew-example-crate/Trunk.toml`, `examples/yew-example-storage/Cargo.toml`, `examples/yew-example-storage/Trunk.toml` 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: identity.distribution | https://github.com/tinysearch/tinysearch - 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/tinysearch/tinysearch/issues/169 - 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/tinysearch/tinysearch/issues/182 - 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/tinysearch/tinysearch/issues/177 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/tinysearch/tinysearch/issues/174 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: 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/tinysearch/tinysearch/issues/173 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/tinysearch/tinysearch/issues/116 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/tinysearch/tinysearch/issues/170 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/tinysearch/tinysearch - 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: community_evidence:github | https://github.com/tinysearch/tinysearch/issues/175 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.