# honcho - 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: `plastic-labs/honcho` - capability: Memory library for building stateful agents - expected_user_outcome: Memory library for building stateful agents ## 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 System Architecture**: importance `high` - source_paths: README.md, src/main.py, src/models.py, src/routers/workspaces.py, src/routers/peers.py - **Self-Hosting, Configuration, and LLM Provider Setup**: importance `high` - source_paths: docker-compose.yml.example, .env.template, config.toml.example, src/config.py, src/schemas/configuration.py - **SDKs, CLI, and Agent Integrations**: importance `high` - source_paths: sdks/python/src/honcho/client.py, sdks/python/src/honcho/aio.py, sdks/python/src/honcho/peer.py, sdks/python/src/honcho/session.py, sdks/python/src/honcho/session_context.py - **Reasoning Pipeline: Deriver, Dreamer, Summarizer, and Retrieval**: importance `high` - source_paths: src/deriver/deriver.py, src/deriver/consumer.py, src/deriver/enqueue.py, src/deriver/queue_manager.py, src/deriver/prompts.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `aa993a6dddce7c5c3372d776d591f33a4cc559f7` - inspected_files: `uv.lock`, `Dockerfile`, `pyproject.toml`, `README.md`, `docs/docs.json`, `docs/README.md`, `docs/package.json`, `docs/v1/README.md`, `docs/v1/openapi.json`, `docs/snippets/overview-shields.mdx`, `docs/snippets/cli-commands.mdx`, `docs/changelog/compatibility-guide.mdx`, `docs/changelog/introduction.mdx`, `docs/v2/README.md`, `docs/v2/openapi.json`, `docs/v3/README.md`, `docs/v3/openapi.json`, `docs/v1/contributing/guidelines.mdx`, `docs/v1/contributing/deploying.mdx`, `docs/v1/contributing/error-handling.mdx` 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/plastic-labs/honcho/issues/725 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/plastic-labs/honcho/issues/494 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission 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/plastic-labs/honcho/issues/789 - 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: Developers should check this installation risk before relying on the project: [Bug] ModuleNotFoundError: No module named 'click' - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: [Bug] ModuleNotFoundError: No module named 'click'. Context: Observed when using python - Why it matters: Developers may fail before the first successful local run: [Bug] ModuleNotFoundError: No module named 'click' - Evidence: failure_mode_cluster:github_issue | https://github.com/plastic-labs/honcho/issues/786 - 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: Developers should check this installation risk before relying on the project: [Feature] Support TurboQuant/turbovec as optional vector store backend for memory compression - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: [Feature] Support TurboQuant/turbovec as optional vector store backend for memory compression. Context: Observed when using node, python, linux - Why it matters: Developers may fail before the first successful local run: [Feature] Support TurboQuant/turbovec as optional vector store backend for memory compression - Evidence: failure_mode_cluster:github_issue | https://github.com/plastic-labs/honcho/issues/781 - 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: Developers should check this installation risk before relying on the project: honcho-cli 0.1.0 on PyPI still missing click — please publish release with #786 fix - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: honcho-cli 0.1.0 on PyPI still missing click — please publish release with #786 fix. Context: Observed when using python, macos - Why it matters: Developers may fail before the first successful local run: honcho-cli 0.1.0 on PyPI still missing click — please publish release with #786 fix - Evidence: failure_mode_cluster:github_issue | https://github.com/plastic-labs/honcho/issues/808 - 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/plastic-labs/honcho/issues/786 - 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/plastic-labs/honcho/issues/781 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/plastic-labs/honcho/issues/808 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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: capability.host_targets | https://github.com/plastic-labs/honcho - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.