# verel - 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: `amitpatole/verel` - capability: Verified agents — nothing is "done" until a grader returns a verdict. Eyes (AgentVision) + verdict bus + compounding memory + a fleet + agent-built tooling + agent-run CI/CD. - expected_user_outcome: Verified agents — nothing is "done" until a grader returns a verdict. Eyes (AgentVision) + verdict bus + compounding memory + a fleet + agent-built tooling + agent-run CI/CD. ## 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 & the Five-Organ Architecture**: importance `high` - source_paths: README.md, docs/ARCHITECTURE.md, docs/SUBSTRATE_DESIGN.md, docs/index.md, docs/unified-architecture.svg - **Verdict Bus, Graders & Self-Healing CI**: importance `high` - source_paths: src/verel/verdict/__init__.py, src/verel/verdict/gate.py, src/verel/verdict/models.py, src/verel/verdict/attest.py, src/verel/verdict/fingerprint.py - **Brain, Scope Lattice & Shared Verified Memory**: importance `high` - source_paths: src/verel/memory/__init__.py, src/verel/memory/lattice.py, src/verel/memory/local.py, src/verel/memory/hosted.py, src/verel/memory/replicated.py - **Fleet, Tool-smith, Surfaces & Operations**: importance `high` - source_paths: src/verel/fleet/__init__.py, src/verel/fleet/manager.py, src/verel/fleet/scheduler.py, src/verel/fleet/worker.py, src/verel/fleet/worktree.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `f44d54b93b6272f09f3b41a2a82ffc26baa994a4` - inspected_files: `README.md`, `pyproject.toml`, `docs/ARCHITECTURE.md`, `docs/H2_RESULTS.md`, `docs/SUBSTRATE_DESIGN.md`, `docs/adoption.md`, `docs/api.md`, `docs/cli.md`, `docs/configuration.md`, `docs/examples.md`, `docs/faq.md`, `docs/getting-started.md`, `docs/index.md`, `docs/tutorial.md`, `docs/usage.md`, `docs/use-cases.md`, `examples/demo_agent_loop.py`, `examples/demo_canary_rollback.py`, `examples/demo_capability_jail.py`, `examples/demo_cicd.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: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: verel doctor: report installed extras and key presence - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: verel doctor: report installed extras and key presence. Context: Observed when using docker - Why it matters: Developers may expose sensitive permissions or credentials: verel doctor: report installed extras and key presence - Evidence: failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/2 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: Add a Rust toolchain (cargo test + clippy) to the CI graders - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add a Rust toolchain (cargo test + clippy) to the CI graders. Context: Observed when using python - Why it matters: Developers may fail before the first successful local run: Add a Rust toolchain (cargo test + clippy) to the CI graders - Evidence: failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v0.28.0 — quorum reads: a point read survives the leader being down - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.28.0 — quorum reads: a point read survives the leader being down. Context: Observed when using node, python - Why it matters: Upgrade or migration may change expected behavior: v0.28.0 — quorum reads: a point read survives the leader being down - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.28.0 - 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: v0.29.0 — security hardening: full attack-surface audit + red-team - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.29.0 — security hardening: full attack-surface audit + red-team. Context: Observed when using python, docker - Why it matters: Upgrade or migration may change expected behavior: v0.29.0 — security hardening: full attack-surface audit + red-team - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.0 - 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: v0.29.1 — security: 3-round adversarial red-team - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.29.1 — security: 3-round adversarial red-team. Context: Observed when using python, docker - Why it matters: Upgrade or migration may change expected behavior: v0.29.1 — security: 3-round adversarial red-team - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.1 - 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: v0.29.2 — CI fix for the v0.29.1 security release - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.29.2 — CI fix for the v0.29.1 security release. Context: Observed when using python, docker - Why it matters: Upgrade or migration may change expected behavior: v0.29.2 — CI fix for the v0.29.1 security release - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.2 - 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: Developers should check this installation risk before relying on the project: v0.30.0 — the verification substrate - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.30.0 — the verification substrate. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v0.30.0 — the verification substrate - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.30.0 - 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: Developers should check this installation risk before relying on the project: v0.31.0 — the shared verified brain - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.31.0 — the shared verified brain. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v0.31.0 — the shared verified brain - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.31.0 - 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: Developers should check this installation risk before relying on the project: v0.32.0 — the authenticated multi-principal brain - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.32.0 — the authenticated multi-principal brain. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v0.32.0 — the authenticated multi-principal brain - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.32.0 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: v0.34.0 — cross-principal verified tier (fact-bound attestation) - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.34.0 — cross-principal verified tier (fact-bound attestation). Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: v0.34.0 — cross-principal verified tier (fact-bound attestation) - Evidence: failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.34.0 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.