# pipenet - 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: `punkpeye/pipenet` - capability: Expose your local server to the public internet instantly - expected_user_outcome: Expose your local server to the public internet instantly ## 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 & Getting Started**: importance `high` - source_paths: README.md, package.json, src/cli.ts, src/pipenet.ts - **Client Architecture**: importance `high` - source_paths: src/Tunnel.ts, src/TunnelCluster.ts, src/HeaderHostTransformer.ts, src/pipenet.ts, src/pipenet.spec.ts - **Server Architecture**: importance `high` - source_paths: src/server/server.ts, src/server/ClientManager.ts, src/server/Client.ts, src/server/TunnelAgent.ts, src/server/index.ts - **Deployment & Cloud Operations**: importance `high` - source_paths: src/server/TunnelServer.ts, src/server/TunnelAgent.ts, src/server/server.ts, src/cli.ts, src/Tunnel.ts ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `d14d96254a0e9ad99edb1dc2ed15cf508092a85d` - inspected_files: `pnpm-lock.yaml`, `README.md`, `package.json`, `src/pipenet.spec.ts`, `src/TunnelCluster.ts`, `src/cli.ts`, `src/Tunnel.ts`, `src/HeaderHostTransformer.ts`, `src/pipenet.ts`, `src/types/human-readable-ids.d.ts`, `src/server/ClientManager.ts`, `src/server/TunnelAgent.ts`, `src/server/ClientManager.spec.ts`, `src/server/Client.ts`, `src/server/TunnelServer.ts`, `src/server/Client.spec.ts`, `src/server/TunnelAgent.spec.ts`, `src/server/index.ts`, `src/server/server.ts`, `src/server/server.spec.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: 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/punkpeye/pipenet/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/punkpeye/pipenet - 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/punkpeye/pipenet - 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/punkpeye/pipenet - 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/punkpeye/pipenet - 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/punkpeye/pipenet - 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/punkpeye/pipenet - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.