# browserable - 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: `browserable/browserable` - capability: Open source and self-hostable browser automation library for AI agents - expected_user_outcome: Open source and self-hostable browser automation library for AI 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, Architecture & Getting Started**: importance `high` - source_paths: README.md, cli/index.js, cli/package.json, deployment/docker-compose.dev.yml, tasks/app.js - **AI Agents, Prompts & LLM Integration**: importance `high` - source_paths: tasks/agents/base.js, tasks/agents/browserable.js, tasks/agents/deepresearch.js, tasks/agents/generative.js, tasks/agents/jarvis.js - **REST API, JavaScript SDK & Custom Functions**: importance `high` - source_paths: sdk/browserable-js/src/index.ts, sdk/browserable-js/src/types.ts, sdk/browserable-js/README.md, sdk/browserable-js/package.json, sdk/examples/js-sdk-test/index.js - **Deployment, Configuration & Troubleshooting**: importance `high` - source_paths: deployment/docker-compose.dev.yml, deployment/.env, deployment/supabase-docker/docker-compose.yml, deployment/supabase-docker/docker-compose.s3.yml, docs/development/environment-variables.md ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `a3af19a66560d8bc3ff2c4ed4f9570eb6a66649c` - inspected_files: `README.md`, `docs/cloud/introduction.mdx`, `docs/development/cli.mdx`, `docs/development/environment-variables.md`, `docs/development/local-development.mdx`, `docs/development/roadmap.mdx`, `docs/development/troubleshooting.mdx`, `docs/docs.json`, `docs/getting-started/demos.mdx`, `docs/getting-started/introduction.mdx`, `docs/guides/admin/api-keys.mdx`, `docs/guides/admin/data-table.mdx`, `docs/guides/admin/flow-chart.mdx`, `docs/guides/admin/llm-calls.mdx`, `docs/guides/admin/task-creation.mdx`, `docs/guides/custom-functions.mdx`, `docs/guides/customization/database.mdx`, `docs/guides/customization/llm.mdx`, `docs/guides/customization/remote-browsers.mdx`, `docs/guides/customization/storage.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/browserable/browserable/issues/20 - 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: capability.host_targets | https://github.com/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/browserable/browserable - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.