coherence-check 0.6.0__tar.gz

coherence_check-0.6.0/LICENSE

@@ -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.

coherence_check-0.6.0/NOTICE

@@ -0,0 +1,4 @@
+Coherence
+Copyright 2026 AurumFlux (A. Kaur)
+
+This product includes software developed by AurumFlux.

coherence_check-0.6.0/PKG-INFO

@@ -0,0 +1,342 @@
+Metadata-Version: 2.4
+Name: coherence-check
+Version: 0.6.0
+Summary: Your AI agent says the work is done. Coherence makes it prove it — evidence, not claims, with tamper-evident CI sessions.
+Author-email: AurumFlux <security@aurumflux.co>
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/aurumflux20/coherence
+Project-URL: Documentation, https://github.com/aurumflux20/coherence/blob/main/docs/INDEX.md
+Project-URL: Repository, https://github.com/aurumflux20/coherence
+Project-URL: Issues, https://github.com/aurumflux20/coherence/issues
+Project-URL: Changelog, https://github.com/aurumflux20/coherence/blob/main/CHANGELOG.md
+Project-URL: Bug Tracker, https://github.com/aurumflux20/coherence/issues
+Keywords: agents,ai,claim,proof,evidence,mcp,code-review,developer-tools,verification
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Security
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Provides-Extra: dev
+Dynamic: license-file
+
+# Coherence
+
+[![CI](https://github.com/aurumflux20/coherence/actions/workflows/ci.yml/badge.svg)](https://github.com/aurumflux20/coherence/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-blue.svg)](https://www.python.org/downloads/)
+
+### Your agent says the work is done. This makes it prove it.
+
+An AI agent writes code and reports back: *"Tests passed. Done."* But "done" was
+a sentence in a chat window, not an exit code. Nobody re-ran it. The spec from
+three messages ago got quietly dropped. The PR is a wall of changes with no
+signal about what actually needs a human's eyes.
+
+Coherence is a small Python library and command-line tool that records the
+difference between **what an agent said** and **what it actually proved** — and
+always keeps a **next step**. It has one rule:
+
+```text
+Nothing is done unless there is evidence.
+Nothing is finished unless there is a next step.
+Nothing is remembered unless it was actually done.
+```
+
+No dependencies. Pure standard library. It runs where your code runs.
+
+---
+
+
+## See it in 10 seconds
+
+```bash
+git clone https://github.com/aurumflux20/coherence && cd coherence
+pip install -e . && python -m coherence tamper-demo
+```
+
+```
+1. An agent runs a check. It FAILS — so no proof is recorded.
+   coherence check  ->  exit 1   (open fact, no evidence)
+
+2. The agent edits its own session file to claim it passed.
+   forged: evidence = "exit_code=0 ..."
+
+3. The check runs again. The hash chain does not match.
+   coherence check  ->  exit 3   TAMPERED at entry 0
+
+A forged green is caught. That is the whole idea.
+```
+
+Runs in a throwaway temp directory; touches nothing of yours.
+
+## Audit a real agent session — the confession is already on disk
+
+Every coding agent writes a full transcript: every command, every real exit
+code. Nobody reads it. `coherence audit` does — it pulls out every checkable
+claim the agent made ("tests pass", "pushed to main") and checks each one
+against what actually ran, in the same file:
+
+```bash
+coherence audit ~/.claude/projects/<your-project>/<session>.jsonl
+```
+
+```
+audited: 735 commands, 74 checkable claims
+
+  supported     20
+  weak evidence 11   (piped exit codes — pytest | tail class)
+  unsupported   41   (claims resting on nothing)
+  CONTRADICTED   2   (claimed success; its own transcript says failure)
+```
+
+That output is real: the auditor's first run was on the 51 MB session of the
+agent that built it. It flagged its own author — two success claims its own
+transcript contradicts, and eleven "tests pass" claims whose only evidence was
+a piped command (`pytest | tail` reports tail's exit code, not pytest's — a
+mistake that same agent had made earlier in the same session).
+
+Verdicts are heuristic pattern-matching, not magic: unusual phrasing slips
+past, and only checkable claims (tests / build / push / commit) are judged.
+The point is the direction of error — a claim with no evidence is flagged for
+a human, never silently trusted. Exit codes: 0 all supported · 1 unsupported ·
+2 contradicted.
+
+---
+
+## What did it touch — and what CAN'T we see?
+
+`audit` catches a lie. `scope` catches a silence: did the agent do anything it
+never mentioned? Reading a transcript can't prove a negative — a single
+`bash deploy.sh` could hide anything — so `coherence scope` never claims full
+visibility. It reports what's readable (files, pushes, hosts, installs) and
+marks what ISN'T as **OPAQUE**, loudly, every time:
+
+```bash
+coherence scope session.jsonl
+```
+
+```
+files touched (394)   repos pushed (13)   network hosts contacted (20)
+
+OPAQUE — effects this report CANNOT see (178)
+  line 428: cd ~/packages/seal && ... storm.py
+      why: runs a program file
+
+VERDICT: BOUNDED — 178 command(s) could do anything this report cannot see.
+```
+
+Same doctrine as the witness above: **unknown never collapses into "clean."**
+A report exits non-zero the moment anything is opaque, even if everything
+visible looks fine — a bounded answer that shows its edge beats a false
+complete one. Real numbers from our own 741-command session, byte-verified
+before publishing: [docs/provenance/](docs/provenance/).
+
+## The problem it fixes
+
+Agents write code fast, so the slow part is now a human checking it. And the
+usual signals lie:
+
+- **"Tests passed"** in a chat message is not the same as a green exit code.
+- A spec agreed at the start of a task gets forgotten halfway through.
+- The agent installed some skill or MCP tool and you have no record of what.
+- A big agent-written PR gives you no idea which line actually matters.
+
+Coherence turns each of those into a **Fact** — a claim, the evidence for it
+(if any), and the next step. A claim with no evidence is simply **not done**,
+and the code enforces that; you can't mark something proven without attaching
+the proof.
+
+**Who it's for:** engineers and tech leads who ship code with AI agents every
+day and are tired of trusting "done" on faith.
+
+---
+
+## Install
+
+```bash
+pip install "git+https://github.com/aurumflux20/coherence.git"
+```
+
+Or for local development:
+
+```bash
+git clone https://github.com/aurumflux20/coherence.git
+cd coherence
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e .
+```
+
+**Requires:** Python 3.10 or newer. **No dependencies** — standard library only.
+
+---
+
+## 60-second look
+
+```bash
+python3 -m coherence law     # the whole idea in three sentences
+python3 storm.py             # the hostile proof — must exit 0
+python3 -m coherence demo    # a worked example
+```
+
+In code:
+
+```python
+from coherence import Coherence
+
+c = Coherence()
+
+# the agent claims something in chat — recorded, but NOT counted as done
+c.said("tests passed", next="actually run pytest and attach the exit code")
+
+# now prove it — evidence attached, so it counts
+c.prove("pytest -q", evidence="exit_code=0", next="chain complete")
+
+print(c.plain_english())
+```
+
+`said()` records a claim with no proof. `prove()` refuses to exist without
+evidence — it will raise rather than let you record a lie.
+
+---
+
+## Stop agents faking a green check in CI
+
+Drop this into a pull-request workflow and an agent can no longer say "all
+green" without the evidence to back it:
+
+```bash
+python3 -m coherence prove-cmd "pytest -q" --claim "unit tests"
+python3 -m coherence check     # exits 1 if any claim is still unproven
+python3 -m coherence report --out coherence-report.md
+```
+
+Copy-paste GitHub Action: [docs/CI.md](docs/CI.md). This repo runs it on its own
+PRs — see `.github/workflows/coherence-pr.yml`.
+
+---
+
+## Proof, not promises
+
+Everything above is tested the hostile way. `storm.py` throws hundreds of
+racing, lying, half-finished claims at the rule and checks it never bends:
+
+```
+[PASS] 500 chat claims → 0 counted as done
+[PASS] a claim with no next step is rejected, 100/100 under a race
+[PASS] memory refuses to store anything that was never proven
+[PASS] CI gate: unproven work fails, proven-only work passes
+RESULT: 7/7 checks PASS
+```
+
+Run it yourself — it must exit 0. Full write-up: [STORM-PROOF.md](STORM-PROOF.md).
+
+---
+
+## GitHub Action — the gate in one block
+
+```yaml
+permissions:
+  pull-requests: write   # for the sticky report comment
+
+steps:
+  - uses: actions/checkout@v4
+  - uses: aurumflux20/coherence@v1
+    with:
+      prove: |
+        pytest -q
+        npm test
+```
+
+Each command becomes evidence. The PR fails on claims without proof, on an
+empty session, or — loudest of all — on a session that was edited after the
+facts were recorded (exit 3). A sticky comment on the PR shows what was proven
+and what is still open, so reviewers see it without installing anything.
+
+---
+
+## Trust boundary — who runs the check
+
+This matters most, so it goes first.
+
+The session file records what was proven. **The protection only holds when
+something the agent does not control runs the check** — normally your CI, not
+the agent under review. If the agent that writes the session can also edit the
+file and then declare itself green, the guarantee is gone.
+
+Coherence closes the tampering half of that: every session entry is
+hash-chained, so editing, deleting, or reordering a recorded fact breaks the
+chain, and `coherence check` fails with exit code 3 at the exact entry that was
+changed — a forged "green" is caught, not trusted.
+
+```bash
+# In CI (not the agent): the check re-verifies the chain before trusting a
+# single fact. A tampered session fails here even if every fact reads "proven".
+coherence check          # exit 0 pass · 1 open facts · 2 empty · 3 tampered
+```
+
+What it still does **not** do: stop an agent that never records a fact at all,
+or one running as the same identity as your CI with write access to the run
+itself. Chaining makes after-the-fact edits detectable; it does not make the
+writer honest. Run the check as a step your agent cannot rewrite.
+
+---
+
+## Honest limits
+
+Printed here so you find them now, not later:
+
+| What it does | What it does not do |
+|---|---|
+| Record claim vs. evidence, always with a next step | Stop a rogue tool that has your keys and ignores it |
+| Run locally, standard library only | Replace GitHub, your CI, or your test runner |
+| Keep an optional lesson memory on disk | Ship as a hosted multi-tenant service |
+
+Coherence records what was proven. It does not *do* the proving for you — you
+still write the test; it just refuses to let "done" mean anything less.
+
+---
+
+## Documentation
+
+| Doc | What's in it |
+|-----|--------------|
+| [docs/INDEX.md](docs/INDEX.md) | Full map |
+| [docs/CI.md](docs/CI.md) | The PR check and badge |
+| [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) | How it's built |
+| [CHANGELOG.md](CHANGELOG.md) | Versions |
+| [SUPPORT.md](SUPPORT.md) | Help + related projects |
+
+Security issues: please report privately per [SECURITY.md](SECURITY.md), not as
+a public issue.
+
+---
+
+## Related projects (separate repos)
+
+| Repo | Role |
+|------|------|
+| [seal](https://github.com/aurumflux20/seal) | Exactly-once admission for agent money actions |
+| [effectfence](https://github.com/aurumflux20/effectfence) | In-process fence against double-firing effects |
+| [fencescan](https://github.com/aurumflux20/fencescan) | Static scan for double-effect risks |
+
+---
+
+## License
+
+**Apache License 2.0** — see [LICENSE](LICENSE).
+
+In plain words: use it, change it, ship it inside your own product, even sell
+something built on top of it — no restrictions, no fees, no asking. This is
+built to help developers; the only ask back is a ⭐ if it did.
+
+© 2026 AurumFlux (A. Kaur)