# slm-mesh - 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: `qualixar/slm-mesh` - capability: Peer-to-peer communication for AI coding agents. 8 MCP tools, full CLI, Python client. Part of the Qualixar research initiative by Varun Pratap Bhardwaj. - expected_user_outcome: Peer-to-peer communication for AI coding agents. 8 MCP tools, full CLI, Python client. Part of the Qualixar research initiative by Varun Pratap Bhardwaj. ## 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 System Architecture**: importance `high` - source_paths: README.md, src/broker/broker.ts, src/broker/broker-entry.ts, src/mcp/server.ts, src/config.ts - **MCP Tools, Claude Code Skills, CLI, and Python Client**: importance `high` - source_paths: src/mcp/server.ts, src/mcp/peer-listener.ts, src/mcp/broker-client.ts, src/mcp/agent-detect.ts, src/cli/cli.ts - **Multi-Machine Setup, WebSocket Transport, and Agent Integrations**: importance `high` - source_paths: docs/multi-machine.md, src/broker/push/ws-server.ts, src/broker/push/manager.ts, src/broker/push/connection.ts, src/broker/push/ndjson.ts - **Configuration, Security, Adapters, and Operations**: importance `medium` - source_paths: src/config.ts, src/broker/port.ts, src/broker/pid.ts, src/broker/token.ts, src/broker/idle.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `7fd37395910cd1144f9eb2f6245910036ce9d9b1` - inspected_files: `README.md`, `package.json`, `docs/api-reference.md`, `docs/architecture.md`, `docs/cli-reference.md`, `docs/configuration.md`, `docs/getting-started.md`, `docs/multi-machine.md`, `docs/python-client.md`, `docs/security.md`, `docs/troubleshooting.md`, `src/adapters/backend.ts`, `src/adapters/memory-bridge.ts`, `src/adapters/slm-bridge.ts`, `src/adapters/sqlite-backend.ts`, `src/broker/broker-entry.ts`, `src/broker/broker.ts`, `src/broker/cleanup.ts`, `src/broker/discovery.ts`, `src/broker/ensure.ts` 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: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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: capability.host_targets | https://github.com/qualixar/slm-mesh - 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/qualixar/slm-mesh - 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/qualixar/slm-mesh - 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/qualixar/slm-mesh - 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/qualixar/slm-mesh - 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/qualixar/slm-mesh - 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/qualixar/slm-mesh - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.