# LaVague - 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: `lavague-ai/LaVague` - capability: Large Action Model framework to develop AI Web Agents - expected_user_outcome: Large Action Model framework to develop AI Web 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 & System Architecture**: importance `high` - source_paths: README.md, lavague-core/lavague/core/__init__.py, lavague-core/lavague/core/agents.py, lavague-core/lavague/core/world_model.py, lavague-core/lavague/core/action_engine.py - **Core Engines: World Model, Navigation, Action & Python Engines**: importance `high` - source_paths: lavague-core/lavague/core/world_model.py, lavague-core/lavague/core/navigation.py, lavague-core/lavague/core/action_engine.py, lavague-core/lavague/core/python_engine.py, lavague-core/lavague/core/base_engine.py - **Drivers, Contexts & Integrations Ecosystem**: importance `high` - source_paths: lavague-core/lavague/core/base_driver.py, lavague-core/lavague/core/context.py, lavague-integrations/drivers/lavague-drivers-selenium/lavague/drivers/selenium/base.py, lavague-integrations/drivers/lavague-drivers-selenium/lavague/drivers/selenium/javascript.py, lavague-integrations/drivers/lavague-drivers-selenium/lavague/drivers/selenium/listener.py - **Developer Tooling: LaVague QA, Test Runner, Server & Gradio**: importance `high` - source_paths: lavague-qa/README.md, lavague-qa/lavague/qa/cli.py, lavague-qa/lavague/qa/generator.py, lavague-qa/lavague/qa/prompts.py, lavague-qa/lavague/qa/utils.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `9024bb832c40291cd012916757f27ef60469b22d` - inspected_files: `README.md`, `pyproject.toml`, `docs/docs/contributing/contributing.md`, `docs/docs/contributing/documentation.md`, `docs/docs/contributing/general.md`, `docs/docs/contributing/template.md`, `docs/docs/examples/hf-papers-retrieval.md`, `docs/docs/examples/job-application.md`, `docs/docs/examples/medical_appointment_booking.md`, `docs/docs/get-started/FAQs.md`, `docs/docs/get-started/customization.md`, `docs/docs/get-started/docs-chrome.md`, `docs/docs/get-started/gradio.md`, `docs/docs/get-started/installation.md`, `docs/docs/get-started/quick-tour.md`, `docs/docs/get-started/testing.md`, `docs/docs/get-started/token-usage.md`, `docs/docs/get-started/troubleshoot.md`, `docs/docs/integrations/anthropic.md`, `docs/docs/integrations/azure.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: 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/lavague-ai/LaVague/issues/642 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Capability evidence risk requires verification - Trigger: Project evidence flags a capability evidence 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/lavague-ai/LaVague/issues/333 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/lavague-ai/LaVague/issues/609 - 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: 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/lavague-ai/LaVague/issues/563 - 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/lavague-ai/LaVague/issues/650 - 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/lavague-ai/LaVague/issues/640 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/lavague-ai/LaVague - 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/lavague-ai/LaVague/issues/641 - 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: evidence.maintainer_signals | https://github.com/lavague-ai/LaVague - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: 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/lavague-ai/LaVague - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.