iops-permissions 0.1.0a2__tar.gz

iops_permissions-0.1.0a2/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Permission Simulator changelog
+
+## 0.1.0a2 — local candidate, unreleased
+
+- A bare `iops-permissions` run by a person at a terminal now opens a first-run
+  wizard: choose a policy, evaluate one action, optionally export a scenario.
+  The preselected answer to every question is the one that writes nothing.
+- A bare run that is not a person is unchanged, byte for byte. The wizard needs
+  both stdin and stdout to be terminals, no `CI` in the environment, `TERM` other
+  than `dumb` and no `IOPS_NO_WIZARD`; anything else still prints the
+  `invalid_arguments` error and exits 2, because a prompt in a pipeline is a hang.
+- Esc or Ctrl-C leaves the terminal as it was found and exits 130 having changed
+  nothing. A console with no byte for a block character gets an ASCII wordmark.
+- No new dependencies: the three declared schema packages are unchanged.
+- Every existing subcommand, flag, JSON payload and exit code is unchanged.
+- Not a gate-reviewed candidate. 0.1.0a1 remains the reviewed one, and the
+  artifact and verification records still describe it.
+
+## 0.1.0a1 — local candidate, unreleased
+
+- Independently installed CLI and Python API for explicit declared-policy analysis.
+- Deterministic allow/deny/approval/unknown decisions with bounded explanations.
+- Provenance-tagged capability findings without complete-authority claims.
+- Policy-only export and explicit protected-file scenario export, verified through
+  real Crash Lab execution using independent product environments.
+- Bounded strict JSON, local schemas, redacted errors and private atomic output.
+
+No execution/enforcement, model calls, framework certification, automatic result
+analysis UI, hosted service or managed cloud. The project license/package name
+decision and final human release approval are recorded separately. No release
+date or published package is claimed by this candidate version.

iops_permissions-0.1.0a2/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.

iops_permissions-0.1.0a2/MANIFEST.in

@@ -0,0 +1,2 @@
+include POLICY_SPEC.md CHANGELOG.md
+recursive-include examples *.json

iops_permissions-0.1.0a2/NOTICE

@@ -0,0 +1,6 @@
+I-Ops Labs
+Copyright 2026 I-Ops Labs contributors
+
+Permission Simulator and Crash Lab are independent I-Ops Labs products.
+Third-party dependencies and official image components retain their own licenses.
+See docs/THIRD_PARTY_LICENSES.md in the source repository for the review record.

iops_permissions-0.1.0a2/PKG-INFO

@@ -0,0 +1,137 @@
+Metadata-Version: 2.4
+Name: iops-permissions
+Version: 0.1.0a2
+Summary: Permission Simulator: local declared-policy analysis and portable test scenarios
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/i-ops-hq/labs/tree/main/products/permissions
+Project-URL: Repository, https://github.com/i-ops-hq/labs
+Project-URL: Issues, https://github.com/i-ops-hq/labs/issues
+Project-URL: Changelog, https://github.com/i-ops-hq/labs/blob/main/products/permissions/CHANGELOG.md
+Classifier: Development Status :: 3 - Alpha
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: jsonschema<5,>=4.23
+Requires-Dist: rfc3339-validator<0.2,>=0.1.4
+Requires-Dist: referencing<1,>=0.35
+Dynamic: license-file
+
+# Permission Simulator — local development alpha
+
+Inspect explicit capability declarations, evaluate structured actions against
+deterministic policy, and export portable policy-oriented test scenarios.
+This package works independently of Crash Lab and other I-Ops products.
+It does not execute an agent or enforce actual runtime permissions.
+
+This project is Apache-2.0 and ships as the distribution and CLI
+`iops-permissions`. That name and licence were selected for local candidate
+0.1.0a1.
+
+## Install and try locally
+
+From this product directory, with uv and Python 3.11+ installed. These commands
+assume a checkout of this repository: the example files they read are part of the
+source tree and are not included in an installed package.
+
+```sh
+export UV_CACHE_DIR="$PWD/../../.cache/uv"
+uv sync --python 3.12 --frozen
+uv run --frozen iops-permissions inspect examples/operations-manifest.json
+uv run --frozen iops-permissions evaluate --policy examples/policy.json --action examples/action-allowed.json --manifest examples/operations-manifest.json
+uv run --frozen iops-permissions evaluate --policy examples/policy.json --action examples/action-denied.json --format text
+```
+
+The last command intentionally exits **3** for denied. Evaluation exits are
+allowed 0, denied 3, requires_approval 4 and unknown 5. Input/I/O errors exit 2;
+unsupported exports exit 6. All decisions are scoped to declared policy and,
+when supplied, manifest coverage. They are not effective permission guarantees.
+
+`action-approval.json`, `action-unknown.json` and `action-api.json` exercise other
+paths. `coding-manifest.json` plus `action-coding.json` demonstrates synthetic
+coding-agent declarations, without claiming a real vendor integration.
+
+```sh
+# Policy-only scenario: requires no runner, adapter or physical test fixture.
+uv run --frozen iops-permissions export --policy examples/policy.json --action examples/action-allowed.json --output /tmp/iops-policy-case.json
+# Isolated test definition: explicitly declares its required fixture and adapter.
+uv run --frozen iops-permissions export --policy examples/policy.json --action examples/action-denied.json --manifest examples/operations-manifest.json --fixture examples/protected-file-fixture.json --output /tmp/iops-protected-case.json
+```
+
+Exports refuse existing output files/symlinks, use private permissions and never
+execute a test. Choose a fresh output filename if those example paths exist.
+The supplied fixture descriptor is test metadata, not an installed fixture or
+verified adapter. Unsupported fixture/action combinations produce no file.
+Generated examples in this directory are actual CLI exports, not execution
+results; their execution_status is not_executed.
+
+## The first run
+
+A bare `iops-permissions`, run by a person at a terminal, opens a short wizard:
+choose a policy, evaluate one action, and optionally export the result as a
+scenario Crash Lab can run. Arrow keys choose, Enter confirms, Esc cancels and
+exits 130 having changed nothing. The preselected answer to every question is
+the one that writes nothing, so holding Enter down finishes the wizard with the
+working directory unchanged.
+
+A bare run that is **not** a person is unchanged. The wizard needs both stdin and
+stdout to be terminals, no `CI` in the environment, `TERM` other than `dumb`, and
+no `IOPS_NO_WIZARD`; anything else prints the `invalid_arguments` JSON error and
+exits 2, exactly as before. These commands run inside CI and inside other agents'
+harnesses, where a prompt is a hang and a hang is worse than an error. Set
+`IOPS_NO_WIZARD=1` to suppress it on an interactive terminal, and `NO_COLOR` to
+drop the colour. Every subcommand, flag, JSON payload and exit code is untouched.
+
+## Python API
+
+As in the quickstart, the files read below are examples from this repository
+rather than package data; substitute your own paths outside a checkout.
+
+```python
+from pathlib import Path
+from iops_permissions import (
+    evaluate,
+    export_scenario,
+    inspect_manifest,
+    loads_policy,
+    loads_action_request,
+    loads_document,
+    loads_fixture_descriptor,
+)
+
+policy = loads_policy(Path("examples/policy.json").read_bytes())
+request = loads_action_request(Path("examples/action-denied.json").read_bytes())
+manifest = loads_document(
+    "capability-manifest", Path("examples/operations-manifest.json").read_bytes()
+)
+result = evaluate(policy, request, manifest)
+assert result.decision == "denied"
+print(result.to_dict())
+exported = export_scenario(policy, request, manifest)
+assert exported.execution_status == "not_executed"
+```
+
+All public input boundaries raise `ContractValidationError` with structured,
+redacted issues. `validate_document` / `loads_document` still support all four
+shared data contracts. `loads_policy`, `loads_action_request`, and
+`loads_fixture_descriptor` validate this product's separate local input formats.
+See [POLICY_SPEC.md](https://github.com/i-ops-hq/labs/blob/main/products/permissions/POLICY_SPEC.md) for selectors, precedence, conservative
+manifest guards, limits and export semantics.
+
+Default reports omit raw resource identifiers/patterns, unknown text, constraint
+text and credential references. IDs must be logical references without secrets.
+Exported scenario files necessarily retain their explicitly selected action
+resource; treat those local artifacts as potentially sensitive configuration.
+
+## Validation and boundaries
+
+```sh
+uv run --frozen pytest -q
+uv build
+```
+
+The repository verifier additionally installs wheels and rebuilt source
+distributions outside the source tree, tests SDK/CLI functionality without Crash
+Lab, and checks matching shared schema bytes. Supported matching is lexical and
+bounded; no regex policy language, path resolution, arbitrary static analysis,
+runtime hooks, enforcement, model calls, gateway, or cloud service is provided.

iops_permissions-0.1.0a2/POLICY_SPEC.md

@@ -0,0 +1,93 @@
+# Permission Simulator local inputs and behavior — v0.1.0
+
+These product-specific inputs do not change the five shared Labs contracts.
+The bundled private schemas define their complete shape. JSON only; no code,
+expressions, external references, YAML, environment expansion or policy plugins.
+All inputs use the existing bounded JSON parser and redacted diagnostics.
+
+## Policy and structured action request
+
+A policy contains schema_version, policy_id, agent_ids (IDs or `*`), an explicit
+default_decision, and up to 256 rules. Each rule has a unique rule_id, effect,
+action_kinds, operations, resource_types and resource_patterns. Selector arrays
+are disjunctions; dimensions are conjunctions. `*` selects all kinds/operations/
+types. Resource patterns are exact strings or literal prefixes with one trailing
+`*`. No regex, glob character classes, `?`, normalization or filesystem access.
+
+An action request contains schema_version, request_id, agent_id and the same
+structured action shape used in Action Event. It is a proposed input only and
+contains no stage or outcome. A supplied manifest must describe the same agent.
+
+All matching rules participate. Precedence is denied > requires_approval >
+unknown > allowed, independent of rule order. The default is used only when no
+rule matches. Explicit default allowed is possible and is reported as a default,
+not an inferred grant. An out-of-scope agent yields unknown. Missing/invalid
+policy, duplicate rule IDs, malformed selectors and unknown fields are errors.
+
+Evaluation uses case-sensitive lexical identifiers only. Dot segments, repeated
+path separators, backslashes, control characters, percent escapes, query strings,
+fragments and user-info markers are unsupported because their interpretation
+could differ from the declared pattern. They yield unknown, never an allow.
+Canonical-looking paths still do not resolve symlinks, OS permissions, endpoint
+authority or indirect effects. A prefix must include `/` when a directory boundary
+is intended: `/workspace/*` differs from `/workspace*`.
+
+## Optional manifest guards and output
+
+The result preserves policy_decision separately from the final scoped decision.
+No manifest means policy-only analysis; it does not assert actual capability.
+With a manifest, a non-denied/non-unknown policy decision requires a supported
+kind/resource capability match. No match, inferred-only matches, unsupported
+patterns in relevant declarations, or uninterpreted constraint text yields
+unknown. A matching approval_required declaration upgrades allowed to approval.
+Explicit denial remains denial regardless of missing capability coverage.
+
+Results include matched rule IDs, matching capability IDs/bases, fixed explanation
+codes and coverage counts/labels. They omit raw resources, patterns, descriptions,
+unknown text, credential references and extensions by default. Logical IDs must
+not contain secrets; the tool is not a general secret detector.
+
+## Bounded findings
+
+Inspect validates a declared manifest and reports: filesystem plus network/API
+coexistence, process plus network/API coexistence, and a literal all-resources
+pattern (`*`). Findings include contributing capability IDs and provenance,
+and say that a chain, write access, exfiltration or actual side effect has not
+been demonstrated. Filesystem action kinds alone do not establish write access.
+Empty results mean these specific checks found nothing, not global safety.
+
+## Scenario export
+
+An explicit policy/action pair exports a deterministic policy_simulation scenario
+using the shared Scenario Definition schema. It records the expected scoped
+decision in its policy constraint and assertion; non-semantic extensions retain
+source IDs and execution/readiness labels. The source policy remains external
+for later re-evaluation; the exported expectation is not an executable policy. The
+`fixture://policy-only` environment is a logical input fixture; no runtime is
+required or executed. Unknown outcomes remain explicitly unknown.
+
+Supplying a fixture descriptor explicitly requests an isolated-execution export.
+The only initial template is protected-file-write: it requires the matching
+agent, an explicit fixture:// identifier and protected resource, a supported
+runtime declaration, an exact selected filesystem write to that protected file,
+and an explicit denied policy decision. Export declares runner/adapter/fixture
+requirements and both a protected-state assertion and an attempted-write assertion,
+so unchanged state alone cannot establish that the test action was exercised.
+These are declarative verifier requirements, not an implemented verifier or a
+claim prerequisites are installed or verified. Mismatches yield a
+typed unsupported export with no scenario and no silent policy-only fallback.
+No export emits an Evidence Result or claims execution success.
+
+## CLI
+
+`iops-permissions inspect MANIFEST`, `evaluate --policy POLICY --action REQUEST
+[--manifest MANIFEST]`, and `export --policy POLICY --action REQUEST
+[--manifest MANIFEST] [--fixture DESCRIPTOR] --output SCENARIO`.
+JSON is default; `--format text` provides a concise human report. Output errors
+are redacted. Evaluation exit codes: allowed 0, denied 3, approval 4, unknown 5;
+input/I/O/usage error 2; unsupported export 6. Inspect/export success is 0.
+Export writes a private local file atomically and refuses overwrite, including
+existing symlinks. Input file reads are bounded and require regular files.
+
+This is a local simulator, not an enforcement integration. No agents, commands,
+fixtures, model calls or artifact references are executed by these commands.

iops_permissions-0.1.0a2/README.md

@@ -0,0 +1,118 @@
+# Permission Simulator — local development alpha
+
+Inspect explicit capability declarations, evaluate structured actions against
+deterministic policy, and export portable policy-oriented test scenarios.
+This package works independently of Crash Lab and other I-Ops products.
+It does not execute an agent or enforce actual runtime permissions.
+
+This project is Apache-2.0 and ships as the distribution and CLI
+`iops-permissions`. That name and licence were selected for local candidate
+0.1.0a1.
+
+## Install and try locally
+
+From this product directory, with uv and Python 3.11+ installed. These commands
+assume a checkout of this repository: the example files they read are part of the
+source tree and are not included in an installed package.
+
+```sh
+export UV_CACHE_DIR="$PWD/../../.cache/uv"
+uv sync --python 3.12 --frozen
+uv run --frozen iops-permissions inspect examples/operations-manifest.json
+uv run --frozen iops-permissions evaluate --policy examples/policy.json --action examples/action-allowed.json --manifest examples/operations-manifest.json
+uv run --frozen iops-permissions evaluate --policy examples/policy.json --action examples/action-denied.json --format text
+```
+
+The last command intentionally exits **3** for denied. Evaluation exits are
+allowed 0, denied 3, requires_approval 4 and unknown 5. Input/I/O errors exit 2;
+unsupported exports exit 6. All decisions are scoped to declared policy and,
+when supplied, manifest coverage. They are not effective permission guarantees.
+
+`action-approval.json`, `action-unknown.json` and `action-api.json` exercise other
+paths. `coding-manifest.json` plus `action-coding.json` demonstrates synthetic
+coding-agent declarations, without claiming a real vendor integration.
+
+```sh
+# Policy-only scenario: requires no runner, adapter or physical test fixture.
+uv run --frozen iops-permissions export --policy examples/policy.json --action examples/action-allowed.json --output /tmp/iops-policy-case.json
+# Isolated test definition: explicitly declares its required fixture and adapter.
+uv run --frozen iops-permissions export --policy examples/policy.json --action examples/action-denied.json --manifest examples/operations-manifest.json --fixture examples/protected-file-fixture.json --output /tmp/iops-protected-case.json
+```
+
+Exports refuse existing output files/symlinks, use private permissions and never
+execute a test. Choose a fresh output filename if those example paths exist.
+The supplied fixture descriptor is test metadata, not an installed fixture or
+verified adapter. Unsupported fixture/action combinations produce no file.
+Generated examples in this directory are actual CLI exports, not execution
+results; their execution_status is not_executed.
+
+## The first run
+
+A bare `iops-permissions`, run by a person at a terminal, opens a short wizard:
+choose a policy, evaluate one action, and optionally export the result as a
+scenario Crash Lab can run. Arrow keys choose, Enter confirms, Esc cancels and
+exits 130 having changed nothing. The preselected answer to every question is
+the one that writes nothing, so holding Enter down finishes the wizard with the
+working directory unchanged.
+
+A bare run that is **not** a person is unchanged. The wizard needs both stdin and
+stdout to be terminals, no `CI` in the environment, `TERM` other than `dumb`, and
+no `IOPS_NO_WIZARD`; anything else prints the `invalid_arguments` JSON error and
+exits 2, exactly as before. These commands run inside CI and inside other agents'
+harnesses, where a prompt is a hang and a hang is worse than an error. Set
+`IOPS_NO_WIZARD=1` to suppress it on an interactive terminal, and `NO_COLOR` to
+drop the colour. Every subcommand, flag, JSON payload and exit code is untouched.
+
+## Python API
+
+As in the quickstart, the files read below are examples from this repository
+rather than package data; substitute your own paths outside a checkout.
+
+```python
+from pathlib import Path
+from iops_permissions import (
+    evaluate,
+    export_scenario,
+    inspect_manifest,
+    loads_policy,
+    loads_action_request,
+    loads_document,
+    loads_fixture_descriptor,
+)
+
+policy = loads_policy(Path("examples/policy.json").read_bytes())
+request = loads_action_request(Path("examples/action-denied.json").read_bytes())
+manifest = loads_document(
+    "capability-manifest", Path("examples/operations-manifest.json").read_bytes()
+)
+result = evaluate(policy, request, manifest)
+assert result.decision == "denied"
+print(result.to_dict())
+exported = export_scenario(policy, request, manifest)
+assert exported.execution_status == "not_executed"
+```
+
+All public input boundaries raise `ContractValidationError` with structured,
+redacted issues. `validate_document` / `loads_document` still support all four
+shared data contracts. `loads_policy`, `loads_action_request`, and
+`loads_fixture_descriptor` validate this product's separate local input formats.
+See [POLICY_SPEC.md](https://github.com/i-ops-hq/labs/blob/main/products/permissions/POLICY_SPEC.md) for selectors, precedence, conservative
+manifest guards, limits and export semantics.
+
+Default reports omit raw resource identifiers/patterns, unknown text, constraint
+text and credential references. IDs must be logical references without secrets.
+Exported scenario files necessarily retain their explicitly selected action
+resource; treat those local artifacts as potentially sensitive configuration.
+
+## Validation and boundaries
+
+```sh
+uv run --frozen pytest -q
+uv build
+```
+
+The repository verifier additionally installs wheels and rebuilt source
+distributions outside the source tree, tests SDK/CLI functionality without Crash
+Lab, and checks matching shared schema bytes. Supported matching is lexical and
+bounded; no regex policy language, path resolution, arbitrary static analysis,
+runtime hooks, enforcement, model calls, gateway, or cloud service is provided.

iops_permissions-0.1.0a2/examples/action-allowed.json

@@ -0,0 +1,13 @@
+{
+  "schema_version": "0.1.0",
+  "request_id": "allowed-request",
+  "agent_id": "python-ops-fixture",
+  "action": {
+    "kind": "filesystem",
+    "operation": "read",
+    "resource": {
+      "type": "file",
+      "identifier": "fixture://protected-workspace/readme.txt"
+    }
+  }
+}

iops_permissions-0.1.0a2/examples/action-api.json

@@ -0,0 +1,13 @@
+{
+  "schema_version": "0.1.0",
+  "request_id": "api-request",
+  "agent_id": "python-ops-fixture",
+  "action": {
+    "kind": "api",
+    "operation": "update",
+    "resource": {
+      "type": "record",
+      "identifier": "fixture://fake-customer-api/customer-1"
+    }
+  }
+}

iops_permissions-0.1.0a2/examples/action-approval.json

@@ -0,0 +1,13 @@
+{
+  "schema_version": "0.1.0",
+  "request_id": "approval-request",
+  "agent_id": "python-ops-fixture",
+  "action": {
+    "kind": "filesystem",
+    "operation": "delete",
+    "resource": {
+      "type": "file",
+      "identifier": "fixture://protected-workspace/scratch.txt"
+    }
+  }
+}

iops_permissions-0.1.0a2/examples/action-coding.json

@@ -0,0 +1,13 @@
+{
+  "schema_version": "0.1.0",
+  "request_id": "coding-read-request",
+  "agent_id": "coding-fixture",
+  "action": {
+    "kind": "filesystem",
+    "operation": "read",
+    "resource": {
+      "type": "file",
+      "identifier": "fixture://protected-workspace/readme.txt"
+    }
+  }
+}