# daytona - 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: `daytonaio/daytona`
- capability: Daytona is a Secure and Elastic Infrastructure for Running AI-Generated Code
- expected_user_outcome: Daytona is a Secure and Elastic Infrastructure for Running AI-Generated Code

## 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, apps/api/src/app.module.ts, apps/runner/cmd/runner/main.go, apps/daemon/cmd/daemon/main.go, apps/dashboard/src/App.tsx
- **Sandboxes: Core Compute Primitive**: importance `high`
  - source_paths: apps/api/src/sandbox/controllers/sandbox.controller.ts, apps/api/src/sandbox/services/sandbox.service.ts, apps/api/src/sandbox/managers/sandbox.manager.ts, apps/api/src/sandbox/managers/sandbox-actions/sandbox-start.action.ts, apps/api/src/sandbox/managers/sandbox-actions/sandbox-stop.action.ts
- **Volumes, Snapshots & Data Persistence**: importance `high`
  - source_paths: apps/api/src/sandbox/controllers/volume.controller.ts, apps/api/src/sandbox/services/volume.service.ts, apps/api/src/sandbox/managers/volume.manager.ts, apps/api/src/sandbox/dto/create-volume.dto.ts, apps/api/src/sandbox/dto/volume.dto.ts
- **Deployment, Runners & Platform Operations**: importance `high`
  - source_paths: docker/docker-compose.yaml, charts/daytona-preview, apps/runner/cmd/runner/main.go, apps/runner/packaging/systemd/daytona-runner.service, apps/runner/packaging/deb/DEBIAN/control

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `7c66e95c8467cbd523806dc22dfe96e46717d2b4`
- inspected_files: `pyproject.toml`, `README.md`, `package.json`, `examples/java/README.md`, `examples/ruby/README.md`, `examples/python/auto-delete/auto_delete.py`, `examples/python/pagination/sandbox.py`, `examples/python/pagination/snapshot.py`, `examples/python/pty/main.py`, `examples/python/lifecycle/lifecycle.py`, `examples/python/charts/main.py`, `examples/python/file-operations/main.py`, `examples/python/region/main.py`, `examples/python/auto-archive/auto_archive.py`, `examples/python/exec-command/exec_session.py`, `examples/python/exec-command/exec_logs_async.py`, `examples/python/exec-command/exec.py`, `examples/python/exec-command/exec_linked.py`, `examples/python/volumes/volume.py`, `examples/python/git-lsp/main.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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- 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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- 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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- 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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- 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: 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 | cevd_43f2dcb000cd4c41bb01cae9aec0f048 | https://github.com/daytonaio/daytona/issues/5013
- 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: 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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- 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: 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 | github_repo:753490180 | https://github.com/daytonaio/daytona
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
