ctrlrun 0.1.0__tar.gz

ctrlrun-0.1.0/CHANGELOG.md

@@ -0,0 +1,73 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project follows
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+Public API names are frozen in `docs/SPEC-v0.1.md` §8. Before 1.0 they may still change, and
+any change to one appears here.
+
+## [Unreleased]
+
+## [0.1.0] — 2026-09-03
+
+First packaged release. The v0.1 kernel is complete: every acceptance test in
+`docs/SPEC-v0.1.md` §7 passes, including the multi-process concurrency test.
+
+### Added
+
+- **Action** — canonical form, `action_hash`, deep-frozen arguments. `float` is rejected in
+  arguments: `0.1` and `0.10` are the same money and different hashes.
+- **Policy** — YAML loader with `ALLOW` / `APPROVE` / `DENY` and fail-closed defaults. An
+  unknown action is denied; there is no default-allow. See the config-breaking rule below
+  for how condition keys are validated.
+- **`@ctrlrun.protect()`** — binds a function call to an Action, evaluates it, and executes
+  from the action's canonical arguments rather than the caller's objects.
+- **Approval binding** — approvals carry the `action_hash` of what a human saw, and are
+  single-use and expiring. A mutated action cannot present an approval granted for another.
+- **Effect key and reservation** — template-resolved effect identity, reserved atomically
+  across processes via `BEGIN IMMEDIATE` and a unique constraint on `effect_key`.
+- **Effect state machine** — `NEW → RESERVED → EXECUTING → COMMITTED | FAILED | AMBIGUOUS`.
+  Only an executor raising `NotExecuted` produces `FAILED`; every other exception, timeouts
+  included, produces `AMBIGUOUS`, and only a human resolves it.
+- **Receipts and events** — portable JSONL evidence for every action.
+- **CLI** — `init`, `demo`, `approve`, `deny`, `receipts`, `effects`, `resolve`.
+- **`ctrlrun demo`** — four failure scenarios, in process, no network.
+- `SECURITY.md` and `docs/CLAIMS.md`, which maps every README claim to its code and test.
+
+### Config-breaking rules
+
+Rules that reject a policy file which an earlier build of this kernel would have loaded.
+A `ctrlrun.yaml` written before this release may need an edit; the process refuses to start
+until it gets one, which is the point.
+
+- **A condition key naming an `Action` field is now a load-time `PolicyError`.** The
+  reserved names are `action_id`, `agent`, `environment`, `principal`, `resource` and
+  `user`. `when: { environment_eq: production }` reads exactly like it scopes a rule to
+  production, and matched nothing at all — conditions address an action's *arguments*, and
+  those are not arguments. Combined with a catch-all `decision: allow` beneath it, a rule
+  that looked restrictive silently permitted everything. If a protected function genuinely
+  takes an argument by one of those names, rename the argument (SPEC-v0.1 §3.2). Only the
+  whole name is reserved: `resource_id_eq` is unaffected.
+- **A condition on an argument the action does not carry now logs a warning.** The decision
+  is unchanged — still false, still never an error, per SPEC-v0.1 §3.2 — but a typo such as
+  `amont_lte` no longer disappears in silence. Nothing to edit; expect new log output.
+
+### Notes
+
+- Requires Python ≥ 3.11. Runtime dependencies are `pyyaml` and `click`.
+- Single-host only: reservation is atomic across processes on one machine via SQLite.
+  Multi-host needs the Postgres store planned for v0.6.
+- Receipts are not signed. A database administrator can alter history (v0.6).
+- Approver identity is free text and is not authenticated (v0.3).
+- Generated ids (`act_`, `apr_`, `ctr_`) are 128 bits. An approval id is not a bearer token
+  in v0.1 — consuming one needs write access to the store — but it becomes one with the
+  webhook provider in v0.2, and an id format cannot be widened after records exist.
+- Effect key templates do not escape placeholder values, so a crafted argument can make two
+  distinct effects share one key. The result is a refusal rather than a double execution;
+  `docs/THREAT_MODEL.md` states the limit and the workaround.
+- Policy conditions address an action's arguments only. Scoping a rule by environment,
+  resource or principal arrives with the authority model in v0.3.
+
+[Unreleased]: https://github.com/CTRLRun/ctrlrun/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/CTRLRun/ctrlrun/releases/tag/v0.1.0

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

ctrlrun-0.1.0/MANIFEST.in

@@ -0,0 +1,22 @@
+# What ships in the sdist beyond the package itself.
+#
+# The tests go in the sdist because a distribution packager builds from it and runs them.
+# That only works if everything they need goes too: `tests/conftest.py` holds the fixtures
+# every store test is parametrized over, and `ctrlrun.example.yaml` is asserted against by
+# `test_the_shipped_example_policy_is_the_one_in_the_repository`. Shipping tests that cannot
+# run is worse than shipping none, so `test_the_sdist_carries_everything_the_tests_need`
+# keeps this file honest.
+
+include ctrlrun.example.yaml
+include CHANGELOG.md
+include SECURITY.md
+include VISION.md
+recursive-include docs *.md
+recursive-include tests *.py
+
+# Local-only: working notes, and anything an operator's run left behind. Nothing here is
+# picked up by default — these are belt and braces, so a stray file cannot ride along.
+prune internal
+prune .ctrlrun
+prune .github
+global-exclude *.py[cod] .DS_Store

ctrlrun-0.1.0/PKG-INFO

@@ -0,0 +1,164 @@
+Metadata-Version: 2.4
+Name: ctrlrun
+Version: 0.1.0
+Summary: Make consequential AI-agent actions safe to execute.
+Author-email: Arpan Ghoshal <contact@arpanghoshal.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/CTRLRun/ctrlrun
+Project-URL: Repository, https://github.com/CTRLRun/ctrlrun
+Project-URL: Documentation, https://github.com/CTRLRun/ctrlrun/tree/main/docs
+Project-URL: Changelog, https://github.com/CTRLRun/ctrlrun/blob/main/CHANGELOG.md
+Project-URL: Issues, https://github.com/CTRLRun/ctrlrun/issues
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pyyaml
+Requires-Dist: click
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: mypy>=2.3; extra == "dev"
+Requires-Dist: ruff>=0.16; extra == "dev"
+Dynamic: license-file
+
+# CTRLRun
+
+**Transaction safety for AI-agent actions.**
+
+> Agents can retry. Your refund shouldn't.
+
+CTRLRun is open-source infrastructure for controlling consequential AI-agent actions.
+
+You decide, per action, what an agent can do autonomously, what requires human approval, and what is blocked.
+
+CTRLRun binds approvals to the exact action, blocks duplicate execution attempts for the same logical effect, stops blind retries when an execution outcome is uncertain, and records what actually happened.
+
+**Autonomy belongs to the action, not the agent.**
+
+---
+
+## The problem
+
+Agents are getting write access to the real world: refunds, emails, deploys, permission grants, record changes. Frameworks already let you approve or deny a tool call. That is not the hard part.
+
+The hard part is what happens at the boundary between *intention* and *effect*:
+
+- A refund commits at Stripe, the response times out, the agent retries. **Did you just refund twice?**
+- A human approves a €500 refund. The agent changes it to €5,000 before executing. **Should that approval still count?**
+- Two agents pick up the same task and issue the same refund. **Which one wins?**
+- A call timed out. Your framework marks it *failed* and retries. **It wasn't failed. It was unknown.**
+
+CTRLRun owns that boundary.
+
+## Quick start
+
+```bash
+pip install ctrlrun
+ctrlrun demo
+```
+
+`ctrlrun demo` runs the four failure scenarios below in well under a second, with no external services.
+
+Protect your first action:
+
+```python
+import ctrlrun
+
+
+@ctrlrun.protect("stripe.refund", effect="refund:{payment_id}")
+def refund(payment_id: str, amount: int, currency: str = "EUR"):
+    return stripe.refunds.create(payment_intent=payment_id, amount=amount)
+```
+
+Configure autonomy per action in `ctrlrun.yaml`:
+
+```yaml
+schema: ctrlrun.policy/v1
+
+actions:
+  customer.read:
+    decision: allow
+
+  stripe.refund:
+    rules:
+      - when: { amount_gte: 0, amount_lte: 50000 }      # up to €500.00
+        decision: allow
+      - when: { amount_gte: 0, amount_lte: 500000 }     # up to €5,000.00
+        decision: approve
+      - decision: deny
+```
+
+Amounts are integer minor units — cents, not euros. Floats are rejected outright, because `0.1` and `0.10` are the same money and different hashes.
+
+Now the same agent can refund €100 on its own, must get a human to approve €2,000, and cannot refund €20,000 at all. Neither can it refund a negative amount, which is a charge wearing a refund's name — an upper bound alone is not a range. Unknown actions are denied. CTRLRun fails closed.
+
+## What `ctrlrun demo` shows
+
+```console
+$ ctrlrun demo
+CTRLRun demo — four ways an agent action goes wrong, and what stops it.
+Policy: refunds up to €1,000 are autonomous, up to €10,000 need a human, above that are denied.
+
+1. Duplicate effect after a lost response
+
+   refund €500  →  remote commits  →  response lost  →  effect: AMBIGUOUS
+   agent retries the same refund
+   ✗ BLOCKED — effect may already have committed; blind retry refused
+   remote refund calls: 1
+   only a human moves it on:  ctrlrun resolve refund:txn_1 --committed|--failed
+
+2. Approval mutation
+
+   agent proposes refund €2,000  →  human approves apr_0aa78e0380ba55d77a601dc782f57095 (bound to the action hash)
+   agent executes refund €5,000  →
+   ✗ BLOCKED — approved action ≠ requested action (mismatch)
+
+3. Concurrent agents, same effect
+
+   Agent A  reserve refund:txn_123  →  ACQUIRED  →  executes
+   Agent B  reserve refund:txn_123  →
+   ✗ BLOCKED — already reserved (in_progress)
+
+4. Approval replay
+
+   approval apr_dbc8bc6f06690cdf2e2c55a4e591ef3b used once  →  consumed
+   same approval presented again                            →
+   ✗ BLOCKED — single-use approval already consumed
+
+Receipts (7): .ctrlrun/demo/receipts.jsonl
+Events:       .ctrlrun/demo/events.jsonl
+
+Read them:    CTRLRUN_STATE=.ctrlrun/demo/state.db ctrlrun receipts
+```
+
+Approval ids are generated per run; everything else is byte-for-byte what the demo prints.
+
+Note scenario 1: **`remote refund calls: 1`**. The refund committed at the remote, the response was lost, and the retry was refused — so the customer was refunded once, not twice. Nothing but a human resolving the effect moves it on.
+
+Every executed action produces a portable JSON receipt: who, what, arguments, decision, approval, effect key, and result (`committed`, `failed`, or `ambiguous`).
+
+## What CTRLRun is not
+
+CTRLRun does not host models, plan, prompt, retrieve, route, remember, or orchestrate. It is not a guardrail library, an IAM system, a workflow engine, or a compliance product. If an agent only reads and answers, you don't need CTRLRun. The moment it can **send, pay, refund, delete, deploy, grant, revoke, approve, submit, purchase, or cancel**, you do.
+
+CTRLRun cannot guarantee exactly-once execution against external systems it doesn't control. It guarantees that it will not *knowingly* execute the same logical effect twice, and that it will never treat an unknown outcome as a failure.
+
+## Documentation
+
+| Doc | Purpose |
+|---|---|
+| [`docs/SPEC-v0.1.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/SPEC-v0.1.md) | The v0.1 contract: models, invariants, acceptance tests |
+| [`docs/ARCHITECTURE.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/ARCHITECTURE.md) | Kernel design and key decisions |
+| [`docs/ROADMAP.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/ROADMAP.md) | v0.1 → v1.0 |
+| [`docs/THREAT_MODEL.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/THREAT_MODEL.md) | What CTRLRun defends against and what it doesn't |
+| [`docs/CLAIMS.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/CLAIMS.md) | Every claim above, mapped to the code and the test that proves it |
+| [`SECURITY.md`](https://github.com/CTRLRun/ctrlrun/blob/main/SECURITY.md) | Reporting a vulnerability |
+| [`VISION.md`](https://github.com/CTRLRun/ctrlrun/blob/main/VISION.md) | Where this can go — not a build spec |
+
+## License
+
+Apache-2.0. The enforcement kernel is and will remain fully open source.

ctrlrun-0.1.0/README.md

@@ -0,0 +1,137 @@
+# CTRLRun
+
+**Transaction safety for AI-agent actions.**
+
+> Agents can retry. Your refund shouldn't.
+
+CTRLRun is open-source infrastructure for controlling consequential AI-agent actions.
+
+You decide, per action, what an agent can do autonomously, what requires human approval, and what is blocked.
+
+CTRLRun binds approvals to the exact action, blocks duplicate execution attempts for the same logical effect, stops blind retries when an execution outcome is uncertain, and records what actually happened.
+
+**Autonomy belongs to the action, not the agent.**
+
+---
+
+## The problem
+
+Agents are getting write access to the real world: refunds, emails, deploys, permission grants, record changes. Frameworks already let you approve or deny a tool call. That is not the hard part.
+
+The hard part is what happens at the boundary between *intention* and *effect*:
+
+- A refund commits at Stripe, the response times out, the agent retries. **Did you just refund twice?**
+- A human approves a €500 refund. The agent changes it to €5,000 before executing. **Should that approval still count?**
+- Two agents pick up the same task and issue the same refund. **Which one wins?**
+- A call timed out. Your framework marks it *failed* and retries. **It wasn't failed. It was unknown.**
+
+CTRLRun owns that boundary.
+
+## Quick start
+
+```bash
+pip install ctrlrun
+ctrlrun demo
+```
+
+`ctrlrun demo` runs the four failure scenarios below in well under a second, with no external services.
+
+Protect your first action:
+
+```python
+import ctrlrun
+
+
+@ctrlrun.protect("stripe.refund", effect="refund:{payment_id}")
+def refund(payment_id: str, amount: int, currency: str = "EUR"):
+    return stripe.refunds.create(payment_intent=payment_id, amount=amount)
+```
+
+Configure autonomy per action in `ctrlrun.yaml`:
+
+```yaml
+schema: ctrlrun.policy/v1
+
+actions:
+  customer.read:
+    decision: allow
+
+  stripe.refund:
+    rules:
+      - when: { amount_gte: 0, amount_lte: 50000 }      # up to €500.00
+        decision: allow
+      - when: { amount_gte: 0, amount_lte: 500000 }     # up to €5,000.00
+        decision: approve
+      - decision: deny
+```
+
+Amounts are integer minor units — cents, not euros. Floats are rejected outright, because `0.1` and `0.10` are the same money and different hashes.
+
+Now the same agent can refund €100 on its own, must get a human to approve €2,000, and cannot refund €20,000 at all. Neither can it refund a negative amount, which is a charge wearing a refund's name — an upper bound alone is not a range. Unknown actions are denied. CTRLRun fails closed.
+
+## What `ctrlrun demo` shows
+
+```console
+$ ctrlrun demo
+CTRLRun demo — four ways an agent action goes wrong, and what stops it.
+Policy: refunds up to €1,000 are autonomous, up to €10,000 need a human, above that are denied.
+
+1. Duplicate effect after a lost response
+
+   refund €500  →  remote commits  →  response lost  →  effect: AMBIGUOUS
+   agent retries the same refund
+   ✗ BLOCKED — effect may already have committed; blind retry refused
+   remote refund calls: 1
+   only a human moves it on:  ctrlrun resolve refund:txn_1 --committed|--failed
+
+2. Approval mutation
+
+   agent proposes refund €2,000  →  human approves apr_0aa78e0380ba55d77a601dc782f57095 (bound to the action hash)
+   agent executes refund €5,000  →
+   ✗ BLOCKED — approved action ≠ requested action (mismatch)
+
+3. Concurrent agents, same effect
+
+   Agent A  reserve refund:txn_123  →  ACQUIRED  →  executes
+   Agent B  reserve refund:txn_123  →
+   ✗ BLOCKED — already reserved (in_progress)
+
+4. Approval replay
+
+   approval apr_dbc8bc6f06690cdf2e2c55a4e591ef3b used once  →  consumed
+   same approval presented again                            →
+   ✗ BLOCKED — single-use approval already consumed
+
+Receipts (7): .ctrlrun/demo/receipts.jsonl
+Events:       .ctrlrun/demo/events.jsonl
+
+Read them:    CTRLRUN_STATE=.ctrlrun/demo/state.db ctrlrun receipts
+```
+
+Approval ids are generated per run; everything else is byte-for-byte what the demo prints.
+
+Note scenario 1: **`remote refund calls: 1`**. The refund committed at the remote, the response was lost, and the retry was refused — so the customer was refunded once, not twice. Nothing but a human resolving the effect moves it on.
+
+Every executed action produces a portable JSON receipt: who, what, arguments, decision, approval, effect key, and result (`committed`, `failed`, or `ambiguous`).
+
+## What CTRLRun is not
+
+CTRLRun does not host models, plan, prompt, retrieve, route, remember, or orchestrate. It is not a guardrail library, an IAM system, a workflow engine, or a compliance product. If an agent only reads and answers, you don't need CTRLRun. The moment it can **send, pay, refund, delete, deploy, grant, revoke, approve, submit, purchase, or cancel**, you do.
+
+CTRLRun cannot guarantee exactly-once execution against external systems it doesn't control. It guarantees that it will not *knowingly* execute the same logical effect twice, and that it will never treat an unknown outcome as a failure.
+
+## Documentation
+
+| Doc | Purpose |
+|---|---|
+| [`docs/SPEC-v0.1.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/SPEC-v0.1.md) | The v0.1 contract: models, invariants, acceptance tests |
+| [`docs/ARCHITECTURE.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/ARCHITECTURE.md) | Kernel design and key decisions |
+| [`docs/ROADMAP.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/ROADMAP.md) | v0.1 → v1.0 |
+| [`docs/THREAT_MODEL.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/THREAT_MODEL.md) | What CTRLRun defends against and what it doesn't |
+| [`docs/CLAIMS.md`](https://github.com/CTRLRun/ctrlrun/blob/main/docs/CLAIMS.md) | Every claim above, mapped to the code and the test that proves it |
+| [`SECURITY.md`](https://github.com/CTRLRun/ctrlrun/blob/main/SECURITY.md) | Reporting a vulnerability |
+| [`VISION.md`](https://github.com/CTRLRun/ctrlrun/blob/main/VISION.md) | Where this can go — not a build spec |
+
+## License
+
+Apache-2.0. The enforcement kernel is and will remain fully open source.

ctrlrun-0.1.0/SECURITY.md

@@ -0,0 +1,38 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Report vulnerabilities privately to **contact@arpanghoshal.com**. Please do not open a public
+issue for a security report.
+
+Include what you need to make the problem reproducible: the version, the policy file, and the
+sequence of actions. A failing test is the fastest possible report.
+
+Expect an acknowledgement within 72 hours and an assessment within seven days. If a fix is
+warranted you will be credited in the release notes unless you ask not to be.
+
+## Supported versions
+
+CTRLRun is pre-1.0. Only the latest release receives fixes.
+
+| Version | Supported |
+|---|---|
+| 0.1.x | yes |
+| < 0.1 | no |
+
+## What counts as a vulnerability
+
+CTRLRun sits in the execution path of consequential actions. Treat anything that breaks one of
+these as a security issue, not a bug:
+
+- An action executes that policy should have denied.
+- An approval authorizes an action other than the exact one a human saw.
+- A consumed, expired, or mismatched approval is accepted.
+- The same logical effect is reserved twice, in any interleaving, across threads or processes.
+- An unknown execution outcome is recorded as `failed` rather than `ambiguous`.
+- A receipt does not reflect what happened.
+
+`docs/THREAT_MODEL.md` states what is deliberately out of scope — a compromised host, a
+malicious administrator with write access to the state database, a lying external service, or
+code that bypasses the decorator entirely. Those are documented limits rather than
+vulnerabilities, but if you think one is stated too generously, say so.