# xurgo-atlas - 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: `JasonCoate/xurgo-atlas` - capability: MCP server for safe, versioned, auditable documentation changes by AI agents - expected_user_outcome: MCP server for safe, versioned, auditable documentation changes by 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 and Quick Start**: importance `high` - source_paths: README.md, AGENTS.md, package.json, src/index.ts, src/cli/init.ts - **Daemon, CLI, and MCP Integration**: importance `high` - source_paths: docs/atlas/daemon-mcp.md, src/cli/daemon.ts, src/cli/mcp-config.ts, src/cli/status.ts, src/mcp/http.ts - **Managed Documentation Lifecycle**: importance `high` - source_paths: AGENTS.md, src/core/ownership.ts, src/core/patch.ts, src/core/policy.ts, src/core/risk.ts - **Storage, Root Safety, and Release Workflow**: importance `medium` - source_paths: docs/atlas/storage-migration.md, docs/atlas/root-worktree-safety.md, docs/atlas/project-resolution-hardening.md, docs/atlas/sqlite-root-safety-ledger.md, docs/atlas/release-checklist.md ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `500a77695416520d3a907016ef864b2c106d097a` - inspected_files: `README.md`, `package.json`, `docs/README.md`, `docs/atlas/daemon-mcp.md`, `docs/atlas/development-workflow.md`, `docs/atlas/lifecycle-state-surfaces.md`, `docs/atlas/project-resolution-hardening.md`, `docs/atlas/readonly-identity-tools.md`, `docs/atlas/release-checklist.md`, `docs/atlas/root-worktree-safety.md`, `docs/atlas/setup.md`, `docs/atlas/sqlite-root-safety-ledger.md`, `docs/atlas/storage-migration.md`, `docs/implementation-checklist.md`, `docs/manifest.yml`, `docs/spec/README.md`, `docs/spec/docu-guard-mcp-kickoff-prompt.md`, `docs/spec/docu-guard-mcp-prd.md`, `docs/spec/docu-guard-mcp-v0.2-daemon-prd.md`, `docs/spec/docu-guard-mcp-v0.2-implementation-plan.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: 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/JasonCoate/xurgo-atlas/issues/1 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: 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/JasonCoate/xurgo-atlas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: 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/JasonCoate/xurgo-atlas - 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: downstream_validation.risk_items | https://github.com/JasonCoate/xurgo-atlas - 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: risks.scoring_risks | https://github.com/JasonCoate/xurgo-atlas - 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 | https://github.com/JasonCoate/xurgo-atlas - 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 | https://github.com/JasonCoate/xurgo-atlas - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.