# pydantic-ai-backend - 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: `vstorm-co/pydantic-ai-backend` - capability: File Storage & Sandbox Backends for Pydantic AI: console tools for file operations, Docker-isolated sandboxes for safe execution, and permission system with presets for access control. Enables secure multi-user handling and testing in agents via in-memory, local, or containerized storage. - expected_user_outcome: File Storage & Sandbox Backends for Pydantic AI: console tools for file operations, Docker-isolated sandboxes for safe execution, and permission system with presets for access control. Enables secure multi-user handling and testing in agents via in-memory, local, or containerized storage. ## 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. - **Project Overview & Architecture**: importance `high` - source_paths: README.md, src/pydantic_ai_backends/__init__.py, src/pydantic_ai_backends/protocol.py, src/pydantic_ai_backends/types.py, mkdocs.yml - **Backends & Protocol Reference**: importance `high` - source_paths: src/pydantic_ai_backends/protocol.py, src/pydantic_ai_backends/backends/state.py, src/pydantic_ai_backends/backends/local.py, src/pydantic_ai_backends/backends/composite.py, src/pydantic_ai_backends/adapter.py - **Console Toolset, Permissions & Capabilities**: importance `high` - source_paths: src/pydantic_ai_backends/toolsets/console.py, src/pydantic_ai_backends/permissions/__init__.py, src/pydantic_ai_backends/permissions/checker.py, src/pydantic_ai_backends/permissions/presets.py, src/pydantic_ai_backends/permissions/types.py - **Sandboxes, Runtimes & Session Management**: importance `high` - source_paths: src/pydantic_ai_backends/backends/base.py, src/pydantic_ai_backends/backends/docker/sandbox.py, src/pydantic_ai_backends/backends/docker/session.py, src/pydantic_ai_backends/backends/docker/runtimes.py, src/pydantic_ai_backends/backends/daytona.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `22297d974615d2688a292696734071e0e51d07cc` - inspected_files: `README.md`, `pyproject.toml`, `docs/api/backends.md`, `docs/api/capability.md`, `docs/api/daytona.md`, `docs/api/docker.md`, `docs/api/index.md`, `docs/api/kubernetes.md`, `docs/api/permissions.md`, `docs/api/toolsets.md`, `docs/api/types.md`, `docs/changelog.md`, `docs/concepts/backends.md`, `docs/concepts/capability.md`, `docs/concepts/console-toolset.md`, `docs/concepts/daytona.md`, `docs/concepts/docker.md`, `docs/concepts/index.md`, `docs/concepts/kubernetes.md`, `docs/concepts/permissions.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: Installation risk requires verification - Trigger: Developers should check this installation risk before relying on the project: 0.2.10 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 0.2.10. Context: Observed when using node, python, docker - Why it matters: Upgrade or migration may change expected behavior: 0.2.10 - Evidence: failure_mode_cluster:github_release | https://github.com/vstorm-co/pydantic-ai-backend/releases/tag/0.2.10 - 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: 0.2.12 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 0.2.12. Context: Observed when using node, docker - Why it matters: Upgrade or migration may change expected behavior: 0.2.12 - Evidence: failure_mode_cluster:github_release | https://github.com/vstorm-co/pydantic-ai-backend/releases/tag/0.2.12 - 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: 0.2.9 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 0.2.9. Context: Observed when using python - Why it matters: Upgrade or migration may change expected behavior: 0.2.9 - Evidence: failure_mode_cluster:github_release | https://github.com/vstorm-co/pydantic-ai-backend/releases/tag/0.2.9 - 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: Bug Report: `LocalBackend.write()` doubles carriage returns on Windows - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Bug Report: `LocalBackend.write()` doubles carriage returns on Windows. Context: Observed when using python, windows - Why it matters: Developers may fail before the first successful local run: Bug Report: `LocalBackend.write()` doubles carriage returns on Windows - Evidence: failure_mode_cluster:github_issue | https://github.com/vstorm-co/pydantic-ai-backend/issues/51 - 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: Dependency Dashboard - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Dependency Dashboard. Context: Observed when using python, docker - Why it matters: Developers may fail before the first successful local run: Dependency Dashboard - Evidence: failure_mode_cluster:github_issue | https://github.com/vstorm-co/pydantic-ai-backend/issues/41 - 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/vstorm-co/pydantic-ai-backend/issues/51 - 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: 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/vstorm-co/pydantic-ai-backend/issues/41 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: 0.2.8 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 0.2.8. Context: Observed when using python, docker - Why it matters: Upgrade or migration may change expected behavior: 0.2.8 - Evidence: failure_mode_cluster:github_release | https://github.com/vstorm-co/pydantic-ai-backend/releases/tag/0.2.8 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/vstorm-co/pydantic-ai-backend - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Runtime risk requires verification - Trigger: Developers should check this runtime risk before relying on the project: 0.2.14 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: 0.2.14. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: 0.2.14 - Evidence: failure_mode_cluster:github_release | https://github.com/vstorm-co/pydantic-ai-backend/releases/tag/0.2.14 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.