problem-frame-gate 0.3.0__tar.gz

problem_frame_gate-0.3.0/.gitignore

@@ -0,0 +1,23 @@
+.venv/
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+coverage.xml
+dist/
+build/
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+*.p12
+*.pfx
+id_rsa
+id_ed25519
+*.sqlite
+*.db
+site/

problem_frame_gate-0.3.0/CITATION.cff

@@ -0,0 +1,14 @@
+cff-version: 1.2.0
+message: "If you use this software, cite the theory paper and this repository."
+title: "Problem Frame Gate"
+version: "0.3.0"
+license: Apache-2.0
+repository-code: "https://github.com/kadubon/problem-frame-gate"
+references:
+  - type: article
+    title: "Problemogenesis Theory: A Finite Proof-Carrying Audit Calculus for Problem-Frame Activation"
+    authors:
+      - family-names: "Takahashi"
+        given-names: "K."
+    doi: "10.5281/zenodo.20913669"
+    date-released: "2026-06-26"

problem_frame_gate-0.3.0/LICENSE

@@ -0,0 +1,175 @@
+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.
+
+"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

problem_frame_gate-0.3.0/NOTICE

@@ -0,0 +1,4 @@
+Problem Frame Gate
+Copyright 2026 Problem Frame Gate contributors
+
+This product includes software developed under the Apache License, Version 2.0.

problem_frame_gate-0.3.0/PKG-INFO

@@ -0,0 +1,153 @@
+Metadata-Version: 2.4
+Name: problem-frame-gate
+Version: 0.3.0
+Summary: Audit logs and action gates for safer AI agents.
+Project-URL: Homepage, https://github.com/kadubon/problem-frame-gate
+Project-URL: Documentation, https://github.com/kadubon/problem-frame-gate/tree/main/docs
+Project-URL: Issues, https://github.com/kadubon/problem-frame-gate/issues
+Project-URL: Source, https://github.com/kadubon/problem-frame-gate
+Author: Problem Frame Gate contributors
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: ai,ai-agents,audit-log,authorization,open-source,provenance,pypi,python,risk-management,security
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+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
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Provides-Extra: dev
+Requires-Dist: bandit>=1.8.6; extra == 'dev'
+Requires-Dist: build>=1.2.2; extra == 'dev'
+Requires-Dist: mypy>=1.16.0; extra == 'dev'
+Requires-Dist: pip-audit>=2.9.0; extra == 'dev'
+Requires-Dist: pytest-cov>=6.2.0; extra == 'dev'
+Requires-Dist: pytest>=8.4.0; extra == 'dev'
+Requires-Dist: ruff>=0.12.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# Problem Frame Gate
+
+Problem Frame Gate is a Python library and CLI for finite, proof-carrying audit
+checks around AI decision frames and external action gates.  It implements the
+audit-calculus concepts in:
+
+Takahashi, K. (2026). *Problemogenesis Theory: A Finite Proof-Carrying Audit
+Calculus for Problem-Frame Activation*. Zenodo.
+https://doi.org/10.5281/zenodo.20913669
+
+The package is strict by default.  A log is not considered safe unless a finite
+manifest declares writer authority, protected action constructors, capacities,
+certificate families, risk modes, and gate bundle policy.
+
+## Install
+
+```bash
+uv sync --all-extras
+uv run pytest
+```
+
+From PyPI:
+
+```bash
+pip install problem-frame-gate
+pfg init-manifest > horizon.json
+```
+
+## Safe Quickstart
+
+Create a strict manifest:
+
+```bash
+pfg init-manifest > horizon.json
+```
+
+Validate and fold a log:
+
+```bash
+pfg validate-schema horizon horizon.json
+pfg validate-schema log log.json
+pfg verify-log --horizon horizon.json log.json
+pfg fold --horizon horizon.json log.json
+```
+
+Check an action gate and emit the atomic bundle:
+
+```bash
+pfg validate-schema gate-request gate-request.json
+pfg check-gate --horizon horizon.json --bundle gate-request.json log.json
+```
+
+The generated bundle contains exactly five protected rows:
+
+1. `GateCheck`
+2. `OutboxClaim`
+3. `UseCap`
+4. `ConsumeResource`
+5. `RiskClose`
+
+Each row must be written by the executor writer and committed in one atomic
+group.  A standalone `OutboxClaim` is rejected.
+
+## Python Example
+
+```python
+from problem_frame_gate import Envelope, EnvelopeClass, ExecutorGate, GateRequest, Horizon
+
+horizon = Horizon.strict_default(agent_writers=("agent",))
+
+def env(eid: str, commit: int, kind: str, **payload: object) -> Envelope:
+    return Envelope(eid, eid, "0", commit, "agent", "agent", 1, EnvelopeClass.NORMAL, {"kind": kind, **payload})
+
+log = [
+    env("e0", 0, "Frame", frame_id="p1", scope="lab", goal="test anomaly",
+        evidence_ids=["u1"], actions=["run-check"], acceptance=["review"], risk_ids=["r1"]),
+    env("e1", 1, "Evidence", evidence_id="u1", digest="sha256:source"),
+    env("e2", 2, "Issue", cert_id="c-risk", family="risk", issuer="agent", expires_at=99, family_check=True),
+    env("e3", 3, "Activated", frame_id="p1"),
+    env("e4", 4, "RiskReg", hypothesis_id="h1", family="fixed"),
+    env("e5", 5, "RiskReserve", risk_id="r1", hypothesis_id="h1", frame_id="p1", eta="1/100"),
+    env("e6", 6, "RiskSpend", risk_id="r1", hypothesis_id="h1", frame_id="p1",
+        eta="1/100", mode="fixed", cert_id="c-risk"),
+    env("e7", 7, "ReserveResource", lease_id="lease1", token_id="tool", frame_id="p1"),
+    env("e8", 8, "MintCap", capability_id="cap1", frame_id="p1", action="run-check"),
+    env("e9", 9, "AuthorizeOutbox", outbox_id="out1", frame_id="p1", action="run-check"),
+]
+
+request = GateRequest(
+    gate_id="gate1", bundle_id="bundle1", frame_id="p1", action="run-check",
+    outbox_id="out1", capability_id="cap1", lease_id="lease1",
+    risk_id="r1", hypothesis_id="h1", risk_mode="fixed", risk_cert_id="c-risk",
+    source_time=9, commit_time=10,
+)
+
+gate = ExecutorGate()
+assert gate.check(horizon, log, request).ok
+bundle = gate.create_bundle(horizon, log, request)
+assert bundle.verify(horizon, log).ok
+```
+
+## Security Boundary
+
+The library proves finite audit consistency.  It does not prove external truth,
+cryptographic collision resistance, statistical model validity, or physical
+effect.  Those are explicit assumptions in checker results.
+
+See `docs/quickstart.md`, `docs/schema.md`, `docs/theory-mapping.md`, and
+`docs/operations.md` for operational use.
+
+## Release
+
+The canonical repository is `https://github.com/kadubon/problem-frame-gate`.
+Versioned releases are published by GitHub Actions through PyPI Trusted
+Publishing from `.github/workflows/workflow.yml`; no long-lived PyPI token is
+required.

problem_frame_gate-0.3.0/README.md

@@ -0,0 +1,116 @@
+# Problem Frame Gate
+
+Problem Frame Gate is a Python library and CLI for finite, proof-carrying audit
+checks around AI decision frames and external action gates.  It implements the
+audit-calculus concepts in:
+
+Takahashi, K. (2026). *Problemogenesis Theory: A Finite Proof-Carrying Audit
+Calculus for Problem-Frame Activation*. Zenodo.
+https://doi.org/10.5281/zenodo.20913669
+
+The package is strict by default.  A log is not considered safe unless a finite
+manifest declares writer authority, protected action constructors, capacities,
+certificate families, risk modes, and gate bundle policy.
+
+## Install
+
+```bash
+uv sync --all-extras
+uv run pytest
+```
+
+From PyPI:
+
+```bash
+pip install problem-frame-gate
+pfg init-manifest > horizon.json
+```
+
+## Safe Quickstart
+
+Create a strict manifest:
+
+```bash
+pfg init-manifest > horizon.json
+```
+
+Validate and fold a log:
+
+```bash
+pfg validate-schema horizon horizon.json
+pfg validate-schema log log.json
+pfg verify-log --horizon horizon.json log.json
+pfg fold --horizon horizon.json log.json
+```
+
+Check an action gate and emit the atomic bundle:
+
+```bash
+pfg validate-schema gate-request gate-request.json
+pfg check-gate --horizon horizon.json --bundle gate-request.json log.json
+```
+
+The generated bundle contains exactly five protected rows:
+
+1. `GateCheck`
+2. `OutboxClaim`
+3. `UseCap`
+4. `ConsumeResource`
+5. `RiskClose`
+
+Each row must be written by the executor writer and committed in one atomic
+group.  A standalone `OutboxClaim` is rejected.
+
+## Python Example
+
+```python
+from problem_frame_gate import Envelope, EnvelopeClass, ExecutorGate, GateRequest, Horizon
+
+horizon = Horizon.strict_default(agent_writers=("agent",))
+
+def env(eid: str, commit: int, kind: str, **payload: object) -> Envelope:
+    return Envelope(eid, eid, "0", commit, "agent", "agent", 1, EnvelopeClass.NORMAL, {"kind": kind, **payload})
+
+log = [
+    env("e0", 0, "Frame", frame_id="p1", scope="lab", goal="test anomaly",
+        evidence_ids=["u1"], actions=["run-check"], acceptance=["review"], risk_ids=["r1"]),
+    env("e1", 1, "Evidence", evidence_id="u1", digest="sha256:source"),
+    env("e2", 2, "Issue", cert_id="c-risk", family="risk", issuer="agent", expires_at=99, family_check=True),
+    env("e3", 3, "Activated", frame_id="p1"),
+    env("e4", 4, "RiskReg", hypothesis_id="h1", family="fixed"),
+    env("e5", 5, "RiskReserve", risk_id="r1", hypothesis_id="h1", frame_id="p1", eta="1/100"),
+    env("e6", 6, "RiskSpend", risk_id="r1", hypothesis_id="h1", frame_id="p1",
+        eta="1/100", mode="fixed", cert_id="c-risk"),
+    env("e7", 7, "ReserveResource", lease_id="lease1", token_id="tool", frame_id="p1"),
+    env("e8", 8, "MintCap", capability_id="cap1", frame_id="p1", action="run-check"),
+    env("e9", 9, "AuthorizeOutbox", outbox_id="out1", frame_id="p1", action="run-check"),
+]
+
+request = GateRequest(
+    gate_id="gate1", bundle_id="bundle1", frame_id="p1", action="run-check",
+    outbox_id="out1", capability_id="cap1", lease_id="lease1",
+    risk_id="r1", hypothesis_id="h1", risk_mode="fixed", risk_cert_id="c-risk",
+    source_time=9, commit_time=10,
+)
+
+gate = ExecutorGate()
+assert gate.check(horizon, log, request).ok
+bundle = gate.create_bundle(horizon, log, request)
+assert bundle.verify(horizon, log).ok
+```
+
+## Security Boundary
+
+The library proves finite audit consistency.  It does not prove external truth,
+cryptographic collision resistance, statistical model validity, or physical
+effect.  Those are explicit assumptions in checker results.
+
+See `docs/quickstart.md`, `docs/schema.md`, `docs/theory-mapping.md`, and
+`docs/operations.md` for operational use.
+
+## Release
+
+The canonical repository is `https://github.com/kadubon/problem-frame-gate`.
+Versioned releases are published by GitHub Actions through PyPI Trusted
+Publishing from `.github/workflows/workflow.yml`; no long-lived PyPI token is
+required.

problem_frame_gate-0.3.0/SECURITY.md

@@ -0,0 +1,27 @@
+# Security Policy
+
+Report vulnerabilities through a private security advisory when the repository
+is hosted on GitHub, or contact the maintainers through the published package
+metadata.
+
+## Scope
+
+This project protects the audit layer.  It checks for secret-looking fields,
+private key blocks, common API key formats, and machine-local paths before
+payloads are accepted by the legal-log verifier.
+
+The package does not provide cryptographic key management, hardware isolation,
+or physical actuator safety by itself.  Those must be supplied by the deployment
+and cited as explicit assumptions in the audit transcript.
+
+## Baseline Checks
+
+Run before publishing or deploying:
+
+```bash
+uv run ruff check .
+uv run mypy
+uv run pytest
+uv run bandit -c pyproject.toml -r src
+uv run pip-audit
+```

problem_frame_gate-0.3.0/docs/ai-agent-quickstart.md

@@ -0,0 +1,21 @@
+# AI Agent Quickstart
+
+Use this package as a final gate before an agent writes to an external system,
+calls a tool with real side effects, starts an experiment, or sends a command to
+an actuator.
+
+## Recommended Flow
+
+1. Append evidence and certificates as envelopes.
+2. Define a decision frame with goal, scope, allowed actions, acceptance
+   criteria, risk ids, and obligations.
+3. Activate the frame only after `check_formation` accepts.
+4. Reserve risk and resources before action.
+5. Mint a single-use capability for one frame and one action.
+6. Authorize one outbox entry.
+7. Call `ExecutorGate.check`.
+8. Append the generated `GateBundle` atomically.
+9. Dispatch only after the bundle is committed.
+
+The key rule is simple: the model may propose actions, but only the gate writes
+the externally actionable claim.

problem_frame_gate-0.3.0/docs/json-format.md

@@ -0,0 +1,78 @@
+# JSON Format
+
+All persistent data is ordinary JSON.  Digests use sorted object keys,
+no insignificant whitespace, UTF-8, and SHA-256 with the prefix `sha256:`.
+
+## Horizon
+
+```json
+{
+  "strict": true,
+  "events": ["e0", "e1"],
+  "causal_order": [["e0", "e1"]],
+  "availability_order": [["e0", "e1"]],
+  "audit_order": [["e0", "e1"]],
+  "capacities": {"normal": 100, "abort": 10, "failClosed": 1},
+  "writer_authority": {
+    "*": ["agent", "executor-gate"],
+    "OutboxClaim": ["executor-gate"]
+  },
+  "version_intervals": {"*": [1, 1]},
+  "commit_groups": {
+    "bundle1": ["bundle1:0", "bundle1:1", "bundle1:2", "bundle1:3", "bundle1:4"]
+  },
+  "protected_constructors": {
+    "GateCheck": ["executor-gate"],
+    "OutboxClaim": ["executor-gate"],
+    "UseCap": ["executor-gate"],
+    "ConsumeResource": ["executor-gate"],
+    "RiskClose": ["executor-gate"]
+  },
+  "gate_bundle_kinds": ["GateCheck", "OutboxClaim", "UseCap", "ConsumeResource", "RiskClose"],
+  "executor_writer": "executor-gate",
+  "clock_policy": "integer-commit-time",
+  "certificate_families": {"risk": ["agent"]},
+  "risk_modes": ["fixed", "selectedEvent", "conditionalSelective", "anytime"],
+  "codebook": ["fixed", "selectedEvent", "conditionalSelective", "anytime"],
+  "allow_local_paths": false
+}
+```
+
+Empty safety tables are rejected in strict mode.  Use `pfg init-manifest` to
+generate a safe starter manifest.
+
+## Envelope
+
+```json
+{
+  "eid": "e8",
+  "event": "e8",
+  "slot": "0",
+  "commit": 8,
+  "writer": "agent",
+  "owner": "agent",
+  "version": 1,
+  "class": "normal",
+  "payload": {
+    "kind": "MintCap",
+    "capability_id": "cap1",
+    "frame_id": "p1",
+    "action": "run-check"
+  },
+  "dependencies": [{"eid": "e3"}],
+  "commit_group": "optional-group"
+}
+```
+
+`payload.kind` is required.  Known object identifiers include `frame_id`,
+`cert_id`, `capability_id`, `risk_id`, `outbox_id`, `lease_id`, `evidence_id`,
+`source_id`, `gate_id`, and `object`.
+
+## CLI
+
+```bash
+pfg digest horizon.json
+pfg scan log.json
+pfg verify-log --horizon horizon.json log.json
+pfg fold --horizon horizon.json log.json
+```

problem_frame_gate-0.3.0/docs/operations.md

@@ -0,0 +1,24 @@
+# Operations
+
+Recommended release checks:
+
+```bash
+uv run ruff check .
+uv run ruff format --check .
+uv run mypy
+uv run pytest
+uv run bandit -c pyproject.toml -r src
+uv run pip-audit
+uv build
+```
+
+Use PyPI trusted publishing.  Avoid long-lived publishing tokens.
+
+Production manifests should pin:
+
+- executor writer id;
+- certificate family issuers;
+- protected action constructors;
+- capacity limits;
+- risk modes;
+- environment assumptions.