# LazyLLM - 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: `LazyAGI/LazyLLM` - capability: Easiest and laziest way for building multi-agent LLMs applications. - expected_user_outcome: Easiest and laziest way for building multi-agent LLMs applications. ## 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. - **LazyLLM Overview and System Architecture**: importance `high` - source_paths: README.md, lazyllm/__init__.py, lazyllm/configs.py, lazyllm/cpp.py, csrc/CMakeLists.txt - **Components, Modules, and Flows**: importance `high` - source_paths: lazyllm/module/module.py, lazyllm/module/llms/trainablemodule.py, lazyllm/module/llms/online_module.py, lazyllm/module/servermodule.py, lazyllm/module/trialmodule.py - **RAG Pipeline, Document Processing, and Stores**: importance `high` - source_paths: lazyllm/tools/rag/document.py, lazyllm/tools/rag/retriever.py, lazyllm/tools/rag/rerank.py, lazyllm/tools/rag/doc_node.py, lazyllm/tools/rag/doc_impl.py - **Agents, Tools, Memory, and Online Model Integration**: importance `high` - source_paths: lazyllm/tools/agent/reactAgent.py, lazyllm/tools/agent/planAndSolveAgent.py, lazyllm/tools/agent/rewooAgent.py, lazyllm/tools/agent/functionCall.py, lazyllm/tools/agent/toolsManager.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `642673c4747dd30c623b09813395c97963a5ac79` - inspected_files: `README.md`, `pyproject.toml`, `requirements.txt`, `docs/add_docstrings.py`, `docs/assets/js/assistant.js`, `docs/assets/js/bot.js`, `docs/assets/js/chatAssistant.js`, `docs/assets/js/jigsaw.js`, `docs/assets/js/lang-redirect.js`, `docs/en/API Reference/cli.md`, `docs/en/API Reference/common.md`, `docs/en/API Reference/components.md`, `docs/en/API Reference/configs.md`, `docs/en/API Reference/data_process.md`, `docs/en/API Reference/flow.md`, `docs/en/API Reference/hook.md`, `docs/en/API Reference/launcher.md`, `docs/en/API Reference/module.md`, `docs/en/API Reference/patch.md`, `docs/en/API Reference/prompt_template.md` 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: 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/LazyAGI/LazyLLM - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/LazyAGI/LazyLLM - 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: no_demo - 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: downstream_validation.risk_items | https://github.com/LazyAGI/LazyLLM - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - 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: risks.scoring_risks | https://github.com/LazyAGI/LazyLLM - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - 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/LazyAGI/LazyLLM - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Maintenance risk requires verification - Trigger: release_recency=unknown。 - 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/LazyAGI/LazyLLM - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.