epistemic-engine 1.2.0__tar.gz

epistemic_engine-1.2.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Aswin S
+
+   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.

epistemic_engine-1.2.0/NOTICE

@@ -0,0 +1,7 @@
+The Epistemic Engine
+Copyright 2026 Aswin S
+
+This product includes software developed by Aswin S.
+
+Licensed under the Apache License, Version 2.0. See the LICENSE file
+for the full terms.

epistemic_engine-1.2.0/PKG-INFO

@@ -0,0 +1,213 @@
+Metadata-Version: 2.4
+Name: epistemic-engine
+Version: 1.2.0
+Summary: Computational epistemology for software: extract code beliefs, verify AI-generated changes, and forecast where confidence will collapse.
+Author: Aswin S
+License: Apache-2.0
+Project-URL: Homepage, https://pypi.org/project/epistemic-engine/
+Project-URL: Documentation, https://pypi.org/project/epistemic-engine/
+Project-URL: Source, https://pypi.org/project/epistemic-engine/
+Keywords: epistemology,belief-revision,agm,static-analysis,software-quality,security,sast,ai-code-review,pre-commit
+Classifier: Development Status :: 4 - Beta
+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
+Requires-Dist: PyYAML>=6.0
+Provides-Extra: parsing
+Requires-Dist: tree-sitter>=0.21; extra == "parsing"
+Requires-Dist: tree-sitter-language-pack>=0.2; extra == "parsing"
+Provides-Extra: rocksdb
+Requires-Dist: rocksdict>=0.3; extra == "rocksdb"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4; extra == "dev"
+Requires-Dist: pytest-cov>=4.1; extra == "dev"
+Dynamic: license-file
+
+# The Epistemic Engine
+
+**Computational epistemology for software.** It reads a codebase as a system of
+*justified beliefs* — claims the code makes about itself ("this function
+authenticates the caller", "this value is never null", "this uses approved
+crypto") — reconstructs how well-justified each one is from git history, and
+tracks how that confidence changes over time.
+
+On top of that foundation it ships two tools you can use today:
+
+- **`ee guard`** — a pre-commit / CI verifier that **blocks unsafe or
+  unjustified code before it lands** (great for reviewing AI-generated changes).
+- **`ee predict-chain`** — forecasts **which beliefs are about to collapse**,
+  why, roughly when, and what it would cost to fix now vs. later — and it
+  **tells you when it can't trust its own forecast.**
+
+Everything is **deterministic** (no LLM, no network, no wall-clock in any
+computed value), runs **offline**, and is backed by **167 tests**.
+
+```bash
+pip install epistemic-engine
+```
+
+Requires Python 3.10+. Apache-2.0 licensed.
+
+---
+
+## What it does, in one screen
+
+```bash
+ee ingest  ./my-repo        # read git history into a local graph
+ee analyze ./my-repo        # extract beliefs, justifications, trajectories
+
+ee guard   ./my-repo --all          # find unsafe / unjustified code
+ee predict-chain ./my-repo          # forecast which beliefs will collapse
+ee dashboard ./my-repo              # explore all of it in your browser
+```
+
+---
+
+## 1. Verify code before it ships — `ee guard`
+
+`ee guard` extracts the beliefs a change makes about itself and **blocks** on
+risky ones, then layers on direct OWASP-class scanners and known-CVE matches.
+Each finding carries a severity, the reason, a concrete fix, and a stable
+fingerprint.
+
+It catches, among others:
+
+| Class | Examples |
+|-------|----------|
+| Weak crypto | `md5`/`sha1`/`mt_rand` used as a security primitive |
+| Injection | SQL built by string concatenation, `os.system`/`popen` on user input |
+| Unsafe sinks | `eval`, `innerHTML`, `unserialize`, `pickle.loads` on untrusted data |
+| Secrets | hardcoded API keys / tokens (the value is never printed or stored) |
+| Misconfig | TLS verification off, `Access-Control-Allow-Origin: *`, debug enabled |
+
+```bash
+ee guard ./repo --staged          # verify staged changes (exit 1 = would block the commit)
+ee guard ./repo --all             # verify the whole tree
+ee guard ./repo --format sarif    # SARIF 2.1.0 for GitHub code scanning
+ee guard ./repo --emit-workflow   # print a ready .github/workflows/ee-guard.yml
+ee hook install ./repo            # run it automatically on every `git commit`
+```
+
+**Adoption features** so it fits a real team: inline `# ee-ignore[rule]`
+suppression, a `disabled_rules` config, and a **baseline** mode
+(`--update-baseline` / `--baseline FILE`) that fails only on *new* findings so
+you can adopt on an existing repo without fixing everything first.
+
+Field-tested on 1,500+ real production files: precision / recall / false-positive
+rate of **1.0 / 1.0 / 0.0** (95% CI lower bound 0.92 on a 114-sample corpus).
+
+---
+
+## 2. Forecast what's about to break — `ee predict-chain`
+
+The engine already knows how each belief's confidence is eroding. `predict-chain`
+projects that forward and, for each at-risk belief, gives you:
+
+- a **causal chain** — the ranked factors driving the predicted collapse, each
+  tagged **measured** (from your repo's history) or **assumption** (your cost model);
+- a **collapse probability** within a horizon, from a seeded Monte Carlo;
+- a **calendar ETA** from your repo's own commit cadence;
+- a **fix + ROI**, computed under *your* cost assumptions and labelled as such.
+
+```bash
+ee predict-chain ./repo --horizon 30    # forecasts with causes, ETA, ROI
+ee calibrate     ./repo                 # is the forecast trustworthy on THIS repo?
+```
+
+**It refuses to lie.** `ee calibrate` runs a leakage-free back-test against your
+repo's own history and reports a Brier **skill score** vs. a base-rate baseline.
+If the model doesn't beat guessing on your repo, the report says so — and
+`predict-chain` prints that verdict above every forecast. It never fabricates
+probabilities for undisclosed future CVEs, and never presents a dollar figure as
+fact.
+
+---
+
+## 3. See everything — `ee dashboard`
+
+```bash
+ee dashboard ./repo      # loopback-only web UI; Ctrl-C to stop
+```
+
+A local, offline, self-contained dashboard with three tabs:
+
+- **Beliefs** — every claim the code makes, by domain, coloured by confidence.
+- **🔮 Predictions** — the collapse forecasts, with the calibration verdict on top.
+- **🛡 Guard** — the `ee guard` findings, grouped by severity, with a BLOCK/PASS
+  banner. Scans the whole repo by default and caches the result.
+
+---
+
+## Why you can trust the output
+
+- **Deterministic.** Identical inputs produce byte-identical output. No LLM, no
+  sampling, no wall-clock in any computed value — so results are reproducible
+  and diffable in CI.
+- **Honest about uncertainty.** Gates are evaluated on the *lower bound* of a
+  Wilson confidence interval, not a point estimate. Predictions ship with a
+  calibration verdict. Cost/ROI figures are labelled assumptions.
+- **Offline-first.** No network access except an explicit `ee sync`.
+- **Bounded formalism.** Beliefs outside the closed PO-1 predicate ontology are
+  recorded as `unformalised` and excluded from reasoning — never silently coerced.
+
+---
+
+## Install
+
+```bash
+pip install epistemic-engine                 # core (zero heavy dependencies)
+pip install "epistemic-engine[parsing]"      # + tree-sitter for entity-level beliefs
+```
+
+Without the `parsing` extra the engine degrades gracefully to file-granularity
+analysis. Python 3.10+.
+
+## Command reference
+
+| Command | What it does |
+|---------|--------------|
+| `ee ingest <repo>` | Read git history into the local epistemic graph |
+| `ee analyze <repo>` | Extract beliefs, justifications, change events, trajectories |
+| `ee guard <repo>` | Verify changed/all code; block unsafe or unjustified beliefs |
+| `ee hook install <repo>` | Install a git pre-commit hook running `ee guard --staged` |
+| `ee predict-chain <repo>` | Forecast belief collapse with causes, ETA, and ROI |
+| `ee calibrate <repo>` | Back-test the forecast model against the repo's own history |
+| `ee dashboard <repo>` | Serve the local web dashboard |
+| `ee report <repo>` | Epistemic health report (text / json / markdown / html) |
+| `ee beliefs / falsifiers / debt / timeline` | Inspect specific slices |
+| `ee doctor` | Validate environment, ontology, and configuration |
+
+Run `ee <command> --help` for options, or `ee man` for a full man page.
+
+## Development
+
+```bash
+git clone <your-repo> && cd epistemic-engine
+pip install -e ".[parsing,dev]"
+pytest                       # 167 tests
+```
+
+## Documented deviations from the design spec
+
+Both are portability choices for a single-developer, offline-first,
+cross-platform (incl. Windows) build; neither changes observable semantics.
+
+- **Graph store** is abstracted behind `storage.GraphStore` with a **SQLite**
+  default backend (zero-install, deterministic); RocksDB is optional.
+- **Git access** goes through the **git CLI** via subprocess, abstracted behind
+  `ingestion.GitExtractor`.
+
+## License
+
+Apache-2.0 © 2026 Aswin S. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

epistemic_engine-1.2.0/README.md

@@ -0,0 +1,177 @@
+# The Epistemic Engine
+
+**Computational epistemology for software.** It reads a codebase as a system of
+*justified beliefs* — claims the code makes about itself ("this function
+authenticates the caller", "this value is never null", "this uses approved
+crypto") — reconstructs how well-justified each one is from git history, and
+tracks how that confidence changes over time.
+
+On top of that foundation it ships two tools you can use today:
+
+- **`ee guard`** — a pre-commit / CI verifier that **blocks unsafe or
+  unjustified code before it lands** (great for reviewing AI-generated changes).
+- **`ee predict-chain`** — forecasts **which beliefs are about to collapse**,
+  why, roughly when, and what it would cost to fix now vs. later — and it
+  **tells you when it can't trust its own forecast.**
+
+Everything is **deterministic** (no LLM, no network, no wall-clock in any
+computed value), runs **offline**, and is backed by **167 tests**.
+
+```bash
+pip install epistemic-engine
+```
+
+Requires Python 3.10+. Apache-2.0 licensed.
+
+---
+
+## What it does, in one screen
+
+```bash
+ee ingest  ./my-repo        # read git history into a local graph
+ee analyze ./my-repo        # extract beliefs, justifications, trajectories
+
+ee guard   ./my-repo --all          # find unsafe / unjustified code
+ee predict-chain ./my-repo          # forecast which beliefs will collapse
+ee dashboard ./my-repo              # explore all of it in your browser
+```
+
+---
+
+## 1. Verify code before it ships — `ee guard`
+
+`ee guard` extracts the beliefs a change makes about itself and **blocks** on
+risky ones, then layers on direct OWASP-class scanners and known-CVE matches.
+Each finding carries a severity, the reason, a concrete fix, and a stable
+fingerprint.
+
+It catches, among others:
+
+| Class | Examples |
+|-------|----------|
+| Weak crypto | `md5`/`sha1`/`mt_rand` used as a security primitive |
+| Injection | SQL built by string concatenation, `os.system`/`popen` on user input |
+| Unsafe sinks | `eval`, `innerHTML`, `unserialize`, `pickle.loads` on untrusted data |
+| Secrets | hardcoded API keys / tokens (the value is never printed or stored) |
+| Misconfig | TLS verification off, `Access-Control-Allow-Origin: *`, debug enabled |
+
+```bash
+ee guard ./repo --staged          # verify staged changes (exit 1 = would block the commit)
+ee guard ./repo --all             # verify the whole tree
+ee guard ./repo --format sarif    # SARIF 2.1.0 for GitHub code scanning
+ee guard ./repo --emit-workflow   # print a ready .github/workflows/ee-guard.yml
+ee hook install ./repo            # run it automatically on every `git commit`
+```
+
+**Adoption features** so it fits a real team: inline `# ee-ignore[rule]`
+suppression, a `disabled_rules` config, and a **baseline** mode
+(`--update-baseline` / `--baseline FILE`) that fails only on *new* findings so
+you can adopt on an existing repo without fixing everything first.
+
+Field-tested on 1,500+ real production files: precision / recall / false-positive
+rate of **1.0 / 1.0 / 0.0** (95% CI lower bound 0.92 on a 114-sample corpus).
+
+---
+
+## 2. Forecast what's about to break — `ee predict-chain`
+
+The engine already knows how each belief's confidence is eroding. `predict-chain`
+projects that forward and, for each at-risk belief, gives you:
+
+- a **causal chain** — the ranked factors driving the predicted collapse, each
+  tagged **measured** (from your repo's history) or **assumption** (your cost model);
+- a **collapse probability** within a horizon, from a seeded Monte Carlo;
+- a **calendar ETA** from your repo's own commit cadence;
+- a **fix + ROI**, computed under *your* cost assumptions and labelled as such.
+
+```bash
+ee predict-chain ./repo --horizon 30    # forecasts with causes, ETA, ROI
+ee calibrate     ./repo                 # is the forecast trustworthy on THIS repo?
+```
+
+**It refuses to lie.** `ee calibrate` runs a leakage-free back-test against your
+repo's own history and reports a Brier **skill score** vs. a base-rate baseline.
+If the model doesn't beat guessing on your repo, the report says so — and
+`predict-chain` prints that verdict above every forecast. It never fabricates
+probabilities for undisclosed future CVEs, and never presents a dollar figure as
+fact.
+
+---
+
+## 3. See everything — `ee dashboard`
+
+```bash
+ee dashboard ./repo      # loopback-only web UI; Ctrl-C to stop
+```
+
+A local, offline, self-contained dashboard with three tabs:
+
+- **Beliefs** — every claim the code makes, by domain, coloured by confidence.
+- **🔮 Predictions** — the collapse forecasts, with the calibration verdict on top.
+- **🛡 Guard** — the `ee guard` findings, grouped by severity, with a BLOCK/PASS
+  banner. Scans the whole repo by default and caches the result.
+
+---
+
+## Why you can trust the output
+
+- **Deterministic.** Identical inputs produce byte-identical output. No LLM, no
+  sampling, no wall-clock in any computed value — so results are reproducible
+  and diffable in CI.
+- **Honest about uncertainty.** Gates are evaluated on the *lower bound* of a
+  Wilson confidence interval, not a point estimate. Predictions ship with a
+  calibration verdict. Cost/ROI figures are labelled assumptions.
+- **Offline-first.** No network access except an explicit `ee sync`.
+- **Bounded formalism.** Beliefs outside the closed PO-1 predicate ontology are
+  recorded as `unformalised` and excluded from reasoning — never silently coerced.
+
+---
+
+## Install
+
+```bash
+pip install epistemic-engine                 # core (zero heavy dependencies)
+pip install "epistemic-engine[parsing]"      # + tree-sitter for entity-level beliefs
+```
+
+Without the `parsing` extra the engine degrades gracefully to file-granularity
+analysis. Python 3.10+.
+
+## Command reference
+
+| Command | What it does |
+|---------|--------------|
+| `ee ingest <repo>` | Read git history into the local epistemic graph |
+| `ee analyze <repo>` | Extract beliefs, justifications, change events, trajectories |
+| `ee guard <repo>` | Verify changed/all code; block unsafe or unjustified beliefs |
+| `ee hook install <repo>` | Install a git pre-commit hook running `ee guard --staged` |
+| `ee predict-chain <repo>` | Forecast belief collapse with causes, ETA, and ROI |
+| `ee calibrate <repo>` | Back-test the forecast model against the repo's own history |
+| `ee dashboard <repo>` | Serve the local web dashboard |
+| `ee report <repo>` | Epistemic health report (text / json / markdown / html) |
+| `ee beliefs / falsifiers / debt / timeline` | Inspect specific slices |
+| `ee doctor` | Validate environment, ontology, and configuration |
+
+Run `ee <command> --help` for options, or `ee man` for a full man page.
+
+## Development
+
+```bash
+git clone <your-repo> && cd epistemic-engine
+pip install -e ".[parsing,dev]"
+pytest                       # 167 tests
+```
+
+## Documented deviations from the design spec
+
+Both are portability choices for a single-developer, offline-first,
+cross-platform (incl. Windows) build; neither changes observable semantics.
+
+- **Graph store** is abstracted behind `storage.GraphStore` with a **SQLite**
+  default backend (zero-install, deterministic); RocksDB is optional.
+- **Git access** goes through the **git CLI** via subprocess, abstracted behind
+  `ingestion.GitExtractor`.
+
+## License
+
+Apache-2.0 © 2026 Aswin S. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

epistemic_engine-1.2.0/pyproject.toml

@@ -0,0 +1,66 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "epistemic-engine"
+version = "1.2.0"
+description = "Computational epistemology for software: extract code beliefs, verify AI-generated changes, and forecast where confidence will collapse."
+readme = "README.md"
+requires-python = ">=3.10"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Aswin S" }]
+keywords = [
+    "epistemology", "belief-revision", "agm", "static-analysis",
+    "software-quality", "security", "sast", "ai-code-review", "pre-commit",
+]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Topic :: Software Development :: Quality Assurance",
+    "Topic :: Security",
+    "Typing :: Typed",
+]
+dependencies = [
+    "PyYAML>=6.0",
+]
+
+[project.urls]
+# Fill these in when you create the hosting page/repo, then re-upload.
+Homepage = "https://pypi.org/project/epistemic-engine/"
+Documentation = "https://pypi.org/project/epistemic-engine/"
+"Source" = "https://pypi.org/project/epistemic-engine/"
+
+[project.optional-dependencies]
+# Tree-sitter grammars are optional: without them the engine degrades to
+# file-granularity analysis (SRS A-3 / degradation modes 3.4), which is required
+# behaviour anyway.
+parsing = [
+    "tree-sitter>=0.21",
+    "tree-sitter-language-pack>=0.2",
+]
+# Optional RocksDB backend (SI-3). SQLite backend is the zero-install default.
+rocksdb = ["rocksdict>=0.3"]
+dev = [
+    "pytest>=7.4",
+    "pytest-cov>=4.1",
+]
+
+[project.scripts]
+ee = "epistemic_engine.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+epistemic_engine = ["ontology/data/*.yaml"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"

epistemic_engine-1.2.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+