program-context-protocol 0.12.4__tar.gz

program_context_protocol-0.12.4/.github/workflows/ci.yml

@@ -0,0 +1,63 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  public-hygiene:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Secret scan
+        # gitleaks/gitleaks-action requires a paid GITLEAKS_LICENSE for
+        # organization repos (free for personal accounts) -- broke silently
+        # the moment this repo transferred from a personal account to the
+        # program-context-protocol org, 2026-08-01. The underlying gitleaks
+        # binary itself is free/OSS regardless of account type; only the
+        # Action wrapper is paywalled. Installing it directly instead,
+        # matching the exact command the local pre-push hook already runs
+        # (.git/hooks/pre-push -- gitleaks detect --source . --no-git -v).
+        run: |
+          GL_VERSION=$(curl -sS https://api.github.com/repos/gitleaks/gitleaks/releases/latest | python3 -c "import json,sys; print(json.load(sys.stdin)['tag_name'].lstrip('v'))")
+          curl -sSfL "https://github.com/gitleaks/gitleaks/releases/download/v${GL_VERSION}/gitleaks_${GL_VERSION}_linux_x64.tar.gz" | tar -xz gitleaks
+          ./gitleaks detect --source . --no-git -v
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.13"
+      - name: No unrelated docs or personal/project references
+        run: python3 scripts/check_public_hygiene.py
+
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      # Several tests build throwaway git repos and commit in them.
+      - name: Configure git identity
+        run: |
+          git config --global user.email "ci@localhost"
+          git config --global user.name "CI"
+
+      - name: Install package
+        run: pip install -e . pytest pytest-mock
+
+      - name: Run test suite
+        run: python -m pytest tests/ -q
+
+      - name: Build wheel
+        run: |
+          pip install build
+          python -m build --wheel

program_context_protocol-0.12.4/.gitignore

@@ -0,0 +1,39 @@
+.DS_Store
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+.env
+node_modules/
+.venv/
+venv/
+.claude/
+hermes_memory.md
+.coverage
+presentations/
+graphify-out/
+
+# --- internal docs & operational data (local-only, launch-prep 2026-07-17) ---
+CLAUDE.md
+AGENTS.md
+pcp.md
+dashboard.html
+hermes_memory.md
+docs/market-research.md
+docs/build-plan.md
+presentations/
+graphify-out/
+.coverage
+.claude/
+
+# PCP's own dogfood/operational state (local-only, never distributed) --
+# this repo runs PCP on itself, but the resulting .pcp/ content is
+# project-specific evidence, not part of the shipped product.
+.pcp/
+docs/market-research-2026-07-modules.md
+docs/build-plan-2026-07.md
+docs/research-ui-intent-2026-07.md
+docs/research-rigidity-vs-reliability-2026-07.md
+docs/CHANGELOG.md
+docs/reviews-*/

program_context_protocol-0.12.4/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

program_context_protocol-0.12.4/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Ganesh Nallasivam
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

program_context_protocol-0.12.4/PKG-INFO

@@ -0,0 +1,123 @@
+Metadata-Version: 2.4
+Name: program-context-protocol
+Version: 0.12.4
+Summary: PCP — prevent LLM hallucination and context drift across dev sessions
+Project-URL: Homepage, https://github.com/program-context-protocol/program-context-protocol
+Project-URL: Repository, https://github.com/program-context-protocol/program-context-protocol
+Project-URL: Issues, https://github.com/program-context-protocol/program-context-protocol/issues
+License: MIT OR Apache-2.0
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+Keywords: agentic-coding,ai-agent,ci-cd,claude-code,context-drift,hallucination,llm,spec-driven-development
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1
+Requires-Dist: jsonschema>=4.21
+Requires-Dist: networkx>=3.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: rich>=13.0
+Provides-Extra: graph
+Requires-Dist: graphifyy>=0.8; extra == 'graph'
+Provides-Extra: visual
+Requires-Dist: playwright>=1.40; extra == 'visual'
+Description-Content-Type: text/markdown
+
+# Program Context Protocol (PCP)
+
+**Your AI coding agent says "done." It isn't.**
+
+Long agent sessions drift: the agent forgets what the objective actually was,
+marks criteria complete that don't work, drops modularity, and nobody catches
+it until it's in production. PCP is a structured `.pcp/` directory + CLI that
+stops this — deterministic CI gates, auto-generated state (never hand-typed,
+never stale), and a validator that checks whether your build actually still
+covers your objective.
+
+If you're searching for: *LLM hallucinated "done"*, *AI agent context drift*,
+*spec drift across dev sessions*, *keep Claude/Copilot/Cursor aligned with
+the objective*, *prevent scope drift in agentic coding* — this is that tool.
+
+## What makes this different
+
+Spec-as-truth (write a spec, build against it) is now common — Spec Kit,
+BMAD, OpenSpec all do it. None of them close the loop:
+
+| Tool | Gap PCP closes |
+|---|---|
+| Spec Kit, OpenSpec, BMAD | Spec-as-truth is mainstream — none block a drifted commit or deploy |
+| Kiro (AWS), Tessl | Proprietary |
+| Swimm, Fiberplane, Grit | Doc-vs-code only, pairwise — no program-level objective coverage |
+| Agent-governance tools (Endor, LaneKeep) | Gate tool calls, not spec alignment |
+
+**Pioneer claim:** `pcp validate-strategy` checks whether your module
+decomposition still collectively covers the stated objective — deterministic
+coupling analysis (circular deps, God modules), not vibes. No other tool in
+this space does this.
+
+## How it works
+
+```
+objective.md (human-approved, immutable to unattended agents)
+     ↓
+strategy/decomposition.md  ←──  pcp validate-strategy
+     ↓
+modules/*/spec.yaml        ←──  pcp validate-module
+     ↓
+[agent codes]
+     ↓
+pre-commit:  pcp check         → Layer 1, deterministic AST/schema, hard block
+PR:          pcp gate          → Layer 2, LLM advisory score, logged
+deploy:      pcp deploy-check  → Layer 3, phase exit criteria, hard block
+```
+
+`current_state.md` and `diff.md` are always auto-generated from your actual
+code — never hand-written, never allowed to go stale.
+
+## Logic-tier ladder — not everything is an LLM's job
+
+Every piece of judgment-requiring logic a PCP-built project writes gets
+routed to the cheapest tool that can correctly make it, cheapest-first:
+
+| Rung | What it is | When it applies |
+|---|---|---|
+| 1. Deterministic | if/else, lookup table | Fixed rules, one correct output |
+| 2. Solver/optimization | OR-Tools, CBC | Constraints+objective known, answer isn't |
+| 3. Statistical/ML | sklearn, HuggingFace | Pattern learned from historical data |
+| 4. RAG | retrieval + light synthesis | Answer exists in a bounded corpus |
+| 5. Cached reuse | lru_cache, diskcache | Replay a near-duplicate prior answer |
+| 6. Deep-think LLM | last resort | Two competent humans would reasonably disagree |
+
+Enforced via schema-validated `logic_tier` fields per acceptance criterion +
+CI drift checks (a criterion that claims rung ≤5 but imports an LLM SDK
+fails the gate). Most agentic-coding tools default everything to rung 6 —
+this is the difference between "call the LLM" and "decide whether you
+should."
+
+## Prior-art gate
+
+Before scaffolding a non-trivial module (auth, payments, queues, parsers,
+state machines, a canvas/diagram editor, PDF processing — anything a mature
+library probably already solves) PCP runs a prior-art check: search
+GitHub/npm/PyPI, shortlist candidates, check license compatibility, decide
+reuse-as-dependency / fork-adapt / reference-pattern-only / build-fresh
+*before* code gets written. Rationale is recorded per module, not left to
+whether the agent happened to think of it that day.
+
+## Install
+
+```
+pip install -e .
+pcp init
+```
+
+Requires `git` and the `claude` CLI on `PATH`. Run `pcp doctor` to check
+your environment.
+
+## Status
+
+Pre-launch — validating across real dogfood projects before a public 1.0.
+Core loop (schema, validate-strategy, scan, Layer 1/2/3 gates) is built and
+tested.
+
+## License
+
+MIT OR Apache-2.0

program_context_protocol-0.12.4/README.md

@@ -0,0 +1,100 @@
+# Program Context Protocol (PCP)
+
+**Your AI coding agent says "done." It isn't.**
+
+Long agent sessions drift: the agent forgets what the objective actually was,
+marks criteria complete that don't work, drops modularity, and nobody catches
+it until it's in production. PCP is a structured `.pcp/` directory + CLI that
+stops this — deterministic CI gates, auto-generated state (never hand-typed,
+never stale), and a validator that checks whether your build actually still
+covers your objective.
+
+If you're searching for: *LLM hallucinated "done"*, *AI agent context drift*,
+*spec drift across dev sessions*, *keep Claude/Copilot/Cursor aligned with
+the objective*, *prevent scope drift in agentic coding* — this is that tool.
+
+## What makes this different
+
+Spec-as-truth (write a spec, build against it) is now common — Spec Kit,
+BMAD, OpenSpec all do it. None of them close the loop:
+
+| Tool | Gap PCP closes |
+|---|---|
+| Spec Kit, OpenSpec, BMAD | Spec-as-truth is mainstream — none block a drifted commit or deploy |
+| Kiro (AWS), Tessl | Proprietary |
+| Swimm, Fiberplane, Grit | Doc-vs-code only, pairwise — no program-level objective coverage |
+| Agent-governance tools (Endor, LaneKeep) | Gate tool calls, not spec alignment |
+
+**Pioneer claim:** `pcp validate-strategy` checks whether your module
+decomposition still collectively covers the stated objective — deterministic
+coupling analysis (circular deps, God modules), not vibes. No other tool in
+this space does this.
+
+## How it works
+
+```
+objective.md (human-approved, immutable to unattended agents)
+     ↓
+strategy/decomposition.md  ←──  pcp validate-strategy
+     ↓
+modules/*/spec.yaml        ←──  pcp validate-module
+     ↓
+[agent codes]
+     ↓
+pre-commit:  pcp check         → Layer 1, deterministic AST/schema, hard block
+PR:          pcp gate          → Layer 2, LLM advisory score, logged
+deploy:      pcp deploy-check  → Layer 3, phase exit criteria, hard block
+```
+
+`current_state.md` and `diff.md` are always auto-generated from your actual
+code — never hand-written, never allowed to go stale.
+
+## Logic-tier ladder — not everything is an LLM's job
+
+Every piece of judgment-requiring logic a PCP-built project writes gets
+routed to the cheapest tool that can correctly make it, cheapest-first:
+
+| Rung | What it is | When it applies |
+|---|---|---|
+| 1. Deterministic | if/else, lookup table | Fixed rules, one correct output |
+| 2. Solver/optimization | OR-Tools, CBC | Constraints+objective known, answer isn't |
+| 3. Statistical/ML | sklearn, HuggingFace | Pattern learned from historical data |
+| 4. RAG | retrieval + light synthesis | Answer exists in a bounded corpus |
+| 5. Cached reuse | lru_cache, diskcache | Replay a near-duplicate prior answer |
+| 6. Deep-think LLM | last resort | Two competent humans would reasonably disagree |
+
+Enforced via schema-validated `logic_tier` fields per acceptance criterion +
+CI drift checks (a criterion that claims rung ≤5 but imports an LLM SDK
+fails the gate). Most agentic-coding tools default everything to rung 6 —
+this is the difference between "call the LLM" and "decide whether you
+should."
+
+## Prior-art gate
+
+Before scaffolding a non-trivial module (auth, payments, queues, parsers,
+state machines, a canvas/diagram editor, PDF processing — anything a mature
+library probably already solves) PCP runs a prior-art check: search
+GitHub/npm/PyPI, shortlist candidates, check license compatibility, decide
+reuse-as-dependency / fork-adapt / reference-pattern-only / build-fresh
+*before* code gets written. Rationale is recorded per module, not left to
+whether the agent happened to think of it that day.
+
+## Install
+
+```
+pip install -e .
+pcp init
+```
+
+Requires `git` and the `claude` CLI on `PATH`. Run `pcp doctor` to check
+your environment.
+
+## Status
+
+Pre-launch — validating across real dogfood projects before a public 1.0.
+Core loop (schema, validate-strategy, scan, Layer 1/2/3 gates) is built and
+tested.
+
+## License
+
+MIT OR Apache-2.0

program_context_protocol-0.12.4/SKILL.md

@@ -0,0 +1,69 @@
+# PCP — Program Context Protocol — Self-Install
+
+You are an LLM that has been told to "implement PCP" or "take over this
+project with PCP." Follow these steps exactly, in order.
+
+## 1. Install
+
+```bash
+cd /tmp
+WHEEL_URL=$(curl -sS https://api.github.com/repos/program-context-protocol/program-context-protocol/releases/latest \
+  | python3 -c "import json,sys; d=json.load(sys.stdin); print([a['browser_download_url'] for a in d['assets'] if a['name'].endswith('.whl')][0])")
+curl -sL -OJ "$WHEEL_URL"
+pip install ./program_context_protocol-*.whl
+```
+
+Resolves the real wheel filename from the latest GitHub Release rather
+than assuming a fixed name — pip validates a wheel's filename structurally
+(`name-version-...`) and rejects anything that isn't a real version, so
+there's no fixed "-latest-" alias to fetch by name; this always installs
+whatever was most recently released.
+
+## 2. Verify the environment
+
+```bash
+pcp doctor --check
+```
+
+This reports which optional tools are available (test runner, linter, SAST
+scanner, `gh` for CI status). Only `git` and the `claude` CLI are required —
+everything else just means the corresponding QA gate will skip until
+installed.
+
+## 3. Take over the project
+
+Write a short vision document (`vision.md`) describing what this project
+should do — plain English is fine. If one already exists in the repo, use
+that. Then, from the project root:
+
+```bash
+pcp takeover vision.md
+```
+
+This single command:
+1. Runs the environment preflight (step 2, repeated automatically).
+2. Generates `.pcp/objective.md`, `architecture.md`, module specs, and CI
+   rules from the vision doc.
+3. Runs `pcp validate-strategy` and shows you coverage/coupling scores.
+4. Asks for your approval before writing anything permanent.
+5. Once approved, autonomously builds every pending acceptance criterion —
+   each one gated by tests, lint, SAST, and an architect-review pass before
+   it's marked complete.
+
+## 4. Ongoing operation
+
+```bash
+pcp watch          # poll CI + deploy health, auto-fix failures
+pcp deploy          # gated deploy: approval prompt, smoke test, auto-rollback
+pcp status --pm     # plain-English progress report, any time
+pcp provenance      # audit-evidence doc — which gates ran, which were skipped/bypassed
+```
+
+## Notes
+
+- Everything PCP does is logged locally under `.pcp/` in the project. No
+  telemetry is sent upstream by default.
+- Re-running `pcp takeover <vision.md>` on a project that already has a
+  `.pcp/` directory will ask before overwriting it (`--force` to skip the
+  prompt).
+- Full command reference: `pcp --help`, or `pcp <command> --help`.

program_context_protocol-0.12.4/pyproject.toml

@@ -0,0 +1,55 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "program-context-protocol"
+version = "0.12.4"
+description = "PCP — prevent LLM hallucination and context drift across dev sessions"
+readme = "README.md"
+keywords = [
+    "llm", "ai-agent", "context-drift", "spec-driven-development",
+    "hallucination", "claude-code", "ci-cd", "agentic-coding",
+]
+license = {text = "MIT OR Apache-2.0"}
+requires-python = ">=3.10"
+dependencies = [
+    "click>=8.1",
+    "pyyaml>=6.0",
+    "jsonschema>=4.21",
+    "rich>=13.0",
+    "networkx>=3.0",
+]
+
+[project.optional-dependencies]
+# Community-detection enrichment on top of validate-strategy's deterministic
+# coupling_score (see coupling.py) — surfaces informal module clusters beyond
+# declared dependencies. Optional: pulls in numpy + ~20 tree-sitter grammars,
+# not needed for the core coupling computation, which only needs networkx.
+graph = ["graphifyy>=0.8"]
+# `visual` acceptance-criterion checks (uat.py's check_visual) — real headless-
+# browser rendering, the one thing dom_contains's static-HTML fetch can't do.
+# Optional: pulls in a Chromium binary via `playwright install`, not needed
+# for anything else in this package.
+visual = ["playwright>=1.40"]
+
+[project.urls]
+Homepage = "https://github.com/program-context-protocol/program-context-protocol"
+Repository = "https://github.com/program-context-protocol/program-context-protocol"
+Issues = "https://github.com/program-context-protocol/program-context-protocol/issues"
+
+[project.scripts]
+pcp = "pcp.cli:cli"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/pcp"]
+artifacts = ["src/pcp/skill_data/**/*.md", "src/pcp/schema/*.schema.json"]
+
+[tool.hatch.envs.default]
+dependencies = [
+    "pytest>=8.0",
+    "pytest-mock>=3.12",
+]
+
+[tool.hatch.envs.default.scripts]
+test = "pytest tests/ -v"