# ReviewBot - 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: `reviewboard/ReviewBot` - capability: A tool for running automated static analysis on code posted to a Review Board instance. - expected_user_outcome: A tool for running automated static analysis on code posted to a Review Board instance. ## 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. - **ReviewBot Overview & System Architecture**: importance `high` - source_paths: README.rst, bot/reviewbot/__init__.py, bot/reviewbot/celery.py, bot/reviewbot/main.py, bot/reviewbot/tasks.py - **Supported Code Checking Tools & Configuration**: importance `high` - source_paths: bot/reviewbot/tools/__init__.py, bot/reviewbot/tools/base/__init__.py, bot/reviewbot/tools/base/tool.py, bot/reviewbot/tools/base/mixins.py, bot/reviewbot/tools/clang.py - **Deployment & Infrastructure**: importance `high` - source_paths: docker/Dockerfile-base, docker/base/Dockerfile, docker/base/scripts/docker-entrypoint.sh, docker/base/scripts/docker-healthcheck.sh, docker/base/scripts/install-tools.sh - **Development, Extensibility & Operations**: importance `medium` - source_paths: bot/reviewbot/tools/base/tool.py, bot/reviewbot/tools/base/mixins.py, bot/reviewbot/tools/base/registry.py, bot/reviewbot/processing/review.py, bot/reviewbot/repositories.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `6fd3bfa1eaf04215a472f1e9392ad7aeb065fb83` - inspected_files: `README.rst`, `docs/releasenotes/_ext/extralinks.py`, `docs/releasenotes/conf.py`, `docs/reviewbot/conf.py` 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/reviewboard/ReviewBot - 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/reviewboard/ReviewBot - 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/reviewboard/ReviewBot - 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/reviewboard/ReviewBot - 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/reviewboard/ReviewBot - 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/reviewboard/ReviewBot - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.