nomosguard 0.1.0__tar.gz

nomosguard-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,42 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Install package (zero runtime deps) and pytest
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e . pytest
+
+      - name: Verify zero runtime dependencies
+        run: |
+          # The core must run with ONLY the stdlib: install into a clean
+          # venv with no extra packages and run the demo.
+          python -m venv /tmp/clean-env
+          /tmp/clean-env/bin/pip install -q --no-deps -e .
+          /tmp/clean-env/bin/python -m nomosguard.demo | python -m json.tool > /dev/null
+          echo "zero-dependency demo OK"
+
+      - name: Run tests
+        run: pytest tests/ -v
+
+      - name: Run demo (smoke)
+        run: python -m nomosguard.demo

nomosguard-0.1.0/.github/workflows/release-pypi.yml

@@ -0,0 +1,77 @@
+name: Release to PyPI
+
+# Fires when a GitHub Release is published. The trusted OIDC publisher must
+# be registered on PyPI (pypi.org/manage/account/publishing) for:
+#   project: nomosguard
+#   owner:   Furox-Art
+#   repo:    nomosguard
+#   workflow: release-pypi.yml
+#   environment: pypi
+# Before that registration, the publish step fails with invalid-publisher —
+# that is expected on the first run; register, then re-publish the release.
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions: {}
+
+jobs:
+  build:
+    name: Build and verify distributions
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install build tooling
+        run: python -m pip install --upgrade build twine
+      - name: Build sdist and wheel
+        run: python -m build
+      - name: Check package metadata
+        run: python -m twine check dist/*
+      - name: Verify the version matches the release tag
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          PKG_VER=$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          echo "release tag: $TAG, package version: $PKG_VER"
+          test "$TAG" = "$PKG_VER"
+      - name: Install built wheel in a clean venv and run the full test suite
+        run: |
+          python -m venv /tmp/clean
+          /tmp/clean/bin/pip install --quiet --no-deps dist/*.whl pytest
+          # zero runtime dependencies: prove the installed package runs on stdlib alone
+          /tmp/clean/bin/python -c "import nomosguard; print('import OK', nomosguard.__version__)"
+          /tmp/clean/bin/python -m nomosguard.demo > /dev/null && echo "demo OK"
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI via trusted OIDC
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      contents: read
+      id-token: write  # OIDC token for trusted publishing
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          persist-credentials: false
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install build tooling
+        run: python -m pip install --upgrade build
+      - name: Build distributions
+        run: python -m build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

nomosguard-0.1.0/.gitignore

@@ -0,0 +1,10 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.venv/
+venv/
+dist/
+build/
+.coverage
+htmlcov/

nomosguard-0.1.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.

nomosguard-0.1.0/PKG-INFO

@@ -0,0 +1,152 @@
+Metadata-Version: 2.5
+Name: nomosguard
+Version: 0.1.0
+Summary: Deterministic security reasoning core: hash-chained evidence ledger, attack-path rule engine, and a fail-closed policy gate. LLMs may produce evidence and explain decisions; they never cross the decision boundary.
+Project-URL: Homepage, https://github.com/Furox-Art/nomosguard
+Project-URL: Documentation, https://github.com/Furox-Art/nomosguard/blob/main/README.md
+Project-URL: Repository, https://github.com/Furox-Art/nomosguard
+Author-email: Furox-Art <177975472+Furox-Art@users.noreply.github.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: agent-security,agent-skills,ai-security,attack-graph,audit-log,deterministic,evidence-ledger,fail-closed,hash-chain,llm,mcp-server,policy-gate,pure-python,reasoning,reproducible,rule-engine,security,tamper-evident,tool-call-guard,zero-dependencies
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Information Technology
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# NomosGuard
+
+**LLM produces evidence. Deterministic machinery decides.**
+
+NomosGuard is a deterministic security reasoning core: an append-only
+evidence ledger, a rule engine that derives threat/access paths from that
+evidence, and a fail-closed policy gate. Language models may *read* events
+and *write* structured claims with cited evidence, and may later *explain*
+decisions in human language — but a model never crosses the decision
+boundary. Every claim without reproducible evidence is discarded; every
+decision is hash-chained; the gate defaults to deny.
+
+The name: *nomos* (νόμος) — Greek for rational law, order derived from
+reason rather than brute force (physis) — plus *guard*, the fail-closed
+gate that enforces it. Together: reasoning that decides, evidence that
+must prove itself.
+
+## Why deterministic core + probabilistic edge
+
+A language model's confidence is not evidence — it is an assertion. This
+project treats it as such:
+
+- **The LLM edge (top):** reads raw events, configuration, CVE records,
+  logs; emits *structured claims* (entities, relations, vulnerabilities,
+  tool calls), each citing the exact evidence fragment (log line hash,
+  config path, CVE ID) that supports it.
+- **The deterministic core:** an append-only, SHA-256 hash-chained ledger
+  stores every claim; a rule engine derives attack/access paths
+  (MulVAL-style logical inference — pure logic, no randomness, no model);
+  a policy gate decides ALLOW / ALERT / BLOCK, fail-closed.
+- **The LLM edge (bottom):** explains the decision, drafts remediation
+  suggestions, and proposes next analysis steps. It narrates; it never
+  decides. If the explanation contradicts the evidence chain, the chain
+  wins.
+
+This is the same separation that makes a court work: a lawyer (the model)
+presents evidence, but the verdict comes from the rules of law (the core),
+and the transcript is tamper-evident.
+
+## Status
+
+Early development — see [VISION.md](VISION.md) for the architecture,
+scope, and first-release boundary. The core (evidence ledger, rule
+engine, policy gate) is implemented with 51 passing tests and a
+reproducible demo scenario, real log ingestion, and a measured benchmark corpus.
+
+### Components
+
+| Module | What it does |
+|---|---|
+| `nomosguard.ledger` | Append-only SHA-256 hash-chained evidence ledger; rejects unevidenced claims; persistent (atomic save, full-chain-verify load) |
+| `nomosguard.rules` | Forward-chaining rule engine with unification; tool-call / CVE / policy extractors |
+| `nomosguard.gate` | Fail-closed policy gate: ALLOW / ALERT / BLOCK with full derivation chains |
+| `nomosguard.ingest.toolcall_jsonl` | Real tool-call JSONL ingestion: each claim cites sha256 of the raw source line |
+| `nomosguard.mcp_server` | MCP session layer: 5 tools (`evidence_ingest`, `assert_claim`, `derive_paths`, `decide`, `explain`) |
+| `nomosguard.mcp_stdio` | JSON-RPC stdio server (`python -m nomosguard.mcp_stdio`) |
+| `nomosguard.benchmark` | Attack-scenario corpus with measured recall / false-positive / fail-closed results |
+| `SKILL.md` | Agent behavioral contract: when to invoke the deterministic chain vs. narrate |
+
+### Benchmark (measured, not asserted)
+
+Run with `python -m nomosguard.benchmark.run_suite_main --output DIR`. The
+corpus is committed and deterministic; the expected outcomes are
+hand-derived from the facts, not produced by the engine. Latest run:
+
+| metric | value |
+|---|---|
+| scenarios | 6 |
+| recall | 2/2 = 100% |
+| false positives | 0 |
+| fail-closed on incomplete evidence | OK |
+| all scenarios passed | yes |
+
+What the corpus does NOT cover (stated honestly): real-world logs, evidence
+tampering *inside* the ledger (that is the ledger's own test suite's job),
+and any scenario requiring an LLM to judge.
+
+### Ingestion
+
+```bash
+python -m nomosguard.ingest.cli examples/sample_toolcalls.jsonl [--ledger PATH]
+```
+
+Every accepted record becomes a claim whose evidence field is
+`sha256:<hex>` of the raw log line — independently verifiable. Malformed
+records are rejected with line number and reason; duplicate lines are
+counted, never re-appended.
+
+
+
+| Module | What it does |
+|---|---|
+| `nomosguard.ledger` | Append-only SHA-256 hash-chained evidence ledger; rejects unevidenced claims |
+| `nomosguard.rules` | Forward-chaining rule engine (MulVAL-style) with tool-call / CVE / policy extractors |
+| `nomosguard.gate` | Fail-closed policy gate: ALLOW / ALERT / BLOCK with full derivation chains |
+| `nomosguard.mcp_server` | MCP session layer: 5 tools (`evidence_ingest`, `assert_claim`, `derive_paths`, `decide`, `explain`) |
+| `nomosguard.mcp_stdio` | JSON-RPC stdio server (`python -m nomosguard.mcp_stdio`) |
+| `SKILL.md` | Agent behavioral contract: when to invoke the deterministic chain vs. narrate |
+
+### Run it
+
+```bash
+pip install -e .
+python -m nomosguard.demo    # committed scenario: derivation + BLOCK
+pytest tests/                # 51 tests incl. full stdio protocol
+python -m nomosguard.benchmark.run_suite_main   # measured recall / false-positive
+```
+
+### Use it from an MCP client
+
+```json
+{"command": "python", "args": ["-m", "nomosguard.mcp_stdio"]}
+```
+
+The server never calls a model. Agents load `SKILL.md` for the behavioral
+contract: assert claims with evidence, derive paths, read the gate
+decision, explain it — never decide it.
+
+## License
+
+Apache-2.0

nomosguard-0.1.0/PLAN.md

@@ -0,0 +1,143 @@
+# NomosGuard — Development Plan (living document)
+
+> Status line is updated as work lands. Every number in this file comes from
+> an actual test run or CI run, never hand-computed.
+
+## Current state (verified 2026-10-09)
+
+**Repository:** https://github.com/Furox-Art/nomosguard (public, Apache-2.0)
+**Version:** 0.1.0 (unreleased — not yet on PyPI)
+**Tests:** 32 passed (core: 30, MCP: 32 incl. stdio protocol)
+**CI:** green on Python 3.10 / 3.11 / 3.12 / 3.13 + zero-dependency check
+**Commits:** f63547c (ledger persistence)
+
+### What exists and is proven
+
+| Component | Module | Proven by |
+|---|---|---|
+| Evidence ledger (in-memory) | `ledger.py` | hash-chain link tests, tamper detection |
+| Evidence ledger (persistent) | `ledger.py` | save/load round-trip, append-after-load, tamper rejection, idempotency (7 tests) |
+| Rule engine (unification) | `rules.py` | variable consistency, head substitution, multi-match firing, unbound-head rejection (7 tests) |
+| Fail-closed policy gate | `gate.py` | fallback BLOCK, block-on-derived-path with full chain |
+| MCP server (5 tools + stdio) | `mcp_server.py`, `mcp_stdio.py` | full JSON-RPC protocol end-to-end test |
+| Agent skill contract | `SKILL.md` | — (behavioral doc) |
+| Vision + architecture doc | `VISION.md` | — |
+
+### What was fixed in this session (both were real defects)
+
+1. **Rule engine matching (commit 1dcb0a8).** The previous Cartesian-product
+   matcher had two correctness bugs: (a) body variables could bind different
+   values in different literals, producing derivations no single evidence
+   chain supports; (b) the head was a constant string, so derived facts lost
+   the component/CVE values (`vulnerable_component` instead of `orders_db`).
+   Rewritten with backtracking unification + head substitution. Demo now
+   derives `Fact(researcher -exposes-> orders_db)`.
+2. **Ledger persistence (commit f63547c).** The chain was in-memory only —
+   it died with the process, defeating the tamper-evidence property it
+   exists for. Now: atomic save, full-chain-verify load, append-continues,
+   MCP `--ledger` flag.
+
+---
+
+## The plan (priority order)
+
+The guiding principle from VISION.md: **one ingestion path done flawlessly
+beats five shallow ones.** The tool-call path is the v1 path. Order is
+correctness-first, then real data, then measurement.
+
+### P1 — Real log ingestion (the promise the project makes)
+
+**Why:** the value proposition is "read real tool-call logs, produce
+evidence-citing claims." Today claims are synthetic in-memory dicts. Until
+a real parser exists, the demo cannot leave the lab.
+
+Deliverables:
+- [ ] `ingest/toolcall_jsonl.py` — parse a JSONL file of MCP tool-call
+      records into ledger claims. Each claim's `evidence` field carries the
+      source line hash (SHA-256 of the raw line), not a paraphrase.
+- [ ] Payload schema validation per claim kind (reject malformed records
+      with a per-record error, never silently skip — the gateway's
+      fail-closed discipline applies to ingestion too).
+- [ ] Ingest demo: committed sample log (synthetic but *realistic* — the
+      same shapes real MCP gateways emit) → parsed → derived → decided.
+- [ ] Tests: parser unit tests (well-formed, malformed, empty-line,
+      duplicate-record idempotency), and an end-to-end ingest→derive→gate test.
+
+Exit criteria: `python -m nomosguard.ingest.toolcall_jsonl sample.jsonl`
+produces a verified ledger; every claim cites a verifiable line hash.
+
+### P2 — Benchmark: attack scenarios with measured catch/miss/false-positive
+
+**Why:** the discipline this project follows (and that the five repos
+released today all share) is: publish real measurements, including null
+results. A security reasoning core with no corpus is unfalsifiable.
+
+Deliverables:
+- [ ] `benchmark/scenarios/` — a committed corpus of tool-call attack
+      scenarios with known ground truth (which paths should be derived,
+      which should not): at minimum (a) vulnerable-component exposure
+      (positive), (b) benign multi-tool workflow (negative — must NOT
+      fire), (c) chained access path 3+ hops deep (positive), (d)
+      incomplete evidence (fail-closed default must apply).
+- [ ] `benchmark/run_suite.py` — measures recall (caught / total positive),
+      false-positive rate, and fail-closed correctness; writes committed
+      JSON + markdown results.
+- [ ] Honesty gate: results page states what the corpus does NOT cover
+      (no real-world logs, no adversarial evidence tampering inside the
+      ledger — that is the ledger's own test's job).
+- [ ] README gets a measured-results section ONLY if numbers support a
+      claim; otherwise the "not yet demonstrated" disclaimer stays.
+
+Exit criteria: corpus runs green in CI; results committed from an actual
+run; limitations stated.
+
+### P3 — Declarative policy configuration
+
+**Why:** `default_rules()` is hardcoded in `mcp_server.py`. A security
+tool whose rules cannot be inspected or versioned outside the code is a
+maintenance trap.
+
+Deliverables:
+- [ ] Policy file format (JSON): rules (Pattern triples) + gate decisions,
+      with a schema validator that rejects malformed rules at load.
+- [ ] `NomosGuardSession.from_policy_file(path)`.
+- [ ] Tests: valid config loads, malformed config rejected with precise
+      error, unknown decision rejected.
+
+### P4 — Ledger hardening
+
+- [ ] Concurrent-append safety note: current design is single-writer;
+      document it, or add file locking. Decide, don't leave ambiguous.
+- [ ] `load` performance on large ledgers: streaming parse + verify
+      instead of read-all (the chain verify is O(n) either way, but memory
+      should be O(1) per entry).
+
+### P5 — First release
+
+- [ ] PyPI trusted publisher (`furox-nomosguard`? — name TBD) + PyPI
+      publish workflow. PyPI/npm release only AFTER P1+P2 land: a first
+      release should ship with the ingestion path and a measured corpus,
+      not before.
+- [ ] GitHub Release notes linking VISION.md + benchmark results.
+
+### Explicitly out of scope (guard against scope creep)
+
+- Real-time network enforcement (batch/stream analysis only)
+- Asset inventory / network topology ingestion (v1 is tool-call only)
+- Any LLM inference inside the core (the whole design forbids it)
+- Multi-writer concurrency (document single-writer instead)
+
+---
+
+## Standing rules for this project (learned the hard way)
+
+1. **Every published number comes from a real run.** No hand-computed
+   figures. If a metric can't be measured, say so.
+2. **The decision boundary is never crossed by a model.** Reviewers' first
+   question is "can an LLM influence the gate?" — the answer must stay no.
+3. **Fail closed.** Missing evidence → BLOCK default. Reject unverifiable
+   chains. Refuse malformed input loudly.
+4. **Zero runtime dependencies.** The core runs on stdlib only; CI checks it
+   in a clean venv. Optional extras (matplotlib-style) never enter the core.
+5. **Honesty sections are mandatory** in any results/doc page: state what
+   was NOT measured and why.