underwrite 0.0.0__tar.gz → 0.0.1__tar.gz

underwrite-0.0.1/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.

underwrite-0.0.1/NOTICE

@@ -0,0 +1,12 @@
+underwrite
+Copyright (C) 2026 ntts9990 (https://github.com/ntts9990)
+
+The underwrite app and underwrite-core are licensed under the Apache License,
+Version 2.0. See LICENSE and LICENSING.md for the terms and file-specific scope.
+This notice is informational and does not modify the license.
+
+"underwrite" is claimed as a trademark of ntts9990. See TRADEMARKS.md and
+Apache License section 6 for the applicable trademark terms.
+
+CODE_OF_CONDUCT.md is adapted from Contributor Covenant 3.0 (CC BY-SA 4.0).
+TRADEMARKS.md is adapted from Model Trademark Guidelines 1.0 (CC BY 4.0).

underwrite-0.0.1/PKG-INFO

@@ -0,0 +1,188 @@
+Metadata-Version: 2.4
+Name: underwrite
+Version: 0.0.1
+Summary: Local evidence normalization, measurement, and acceptance checks
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: underwrite-core>=0.0.1,<0.1
+Requires-Dist: jsonschema>=4.26.0
+Requires-Dist: pyyaml>=6.0.3
+Requires-Python: >=3.12
+Project-URL: Repository, https://github.com/ntts9990/underwrite
+Project-URL: Issues, https://github.com/ntts9990/underwrite/issues
+Description-Content-Type: text/markdown
+
+# underwrite
+
+underwrite turns local evaluation artifacts into a common observation, computes
+measurements under an explicit policy, and classifies change candidates against
+declared evidence. It keeps missing evidence visible: `not_measured`,
+`indeterminate`, and `abstained` are distinct outcomes.
+
+It is a Python CLI and library. Artifact inspection checks bytes and declared
+hashes; release checks examine declared linkage and record presence. These checks
+do not establish independent provenance or grant deployment permission.
+
+## Install from source
+
+Requires Python 3.12 or later and [uv](https://docs.astral.sh/uv/).
+
+```sh
+git clone https://github.com/ntts9990/underwrite.git
+cd underwrite
+uv sync --frozen --all-groups
+uv run --frozen --no-sync underwrite --help
+```
+
+The repository includes the `underwrite-core` workspace package. No adjacent
+checkout is needed to install or use the example workflows.
+
+## PyPI release preparation
+
+The functional `0.0.1` release is prepared for `underwrite-core` and `underwrite`;
+publication is not yet confirmed. The existing `underwrite` `0.0.0` entry is a
+reserved placeholder. Use the source installation above until both `0.0.1`
+releases are available. After publication, the planned CLI installation is:
+
+```sh
+uv tool install 'underwrite==0.0.1'
+underwrite --help
+```
+
+Maintainers: create the GitHub environment `pypi`, restrict it to `main`, and
+configure a PyPI GitHub Trusted Publisher on each project with owner `ntts9990`,
+repository `underwrite`, workflow filename `publish.yml`, and environment `pypi`.
+For the new `underwrite-core` project, register a pending publisher under that
+project name; add the publisher to the existing `underwrite` project in its
+Publishing settings. No stored PyPI API token is required.
+
+Once configured, run **Publish PyPI** manually from the `main` branch in
+GitHub Actions. It tests both packages, builds and validates the exact
+distributions, and installs the wheels in a clean
+environment before publishing core and then the application. Only the separate
+publish job receives OIDC permission. Retry with the same artifacts after a
+partial upload; existing registry files must match exactly. A changed artifact
+requires a new version. Confirm both PyPI project releases and a fresh indexed
+installation before describing the release as available.
+
+The workflow follows the official [uv publishing guide](https://docs.astral.sh/uv/guides/package/)
+and [PyPI Trusted Publisher guide](https://docs.pypi.org/trusted-publishers/using-a-publisher/).
+
+## Normalize an artifact
+
+Choose a format and exact supported version explicitly:
+
+| Producer | `--format` | `--version` |
+| --- | --- | --- |
+| DeepEval | `deepeval.test-run` | `4.1.1` |
+| Inspect AI | `inspect.eval-log` | `0.3.263` |
+| Langfuse | `langfuse.observations-v2` or `langfuse.scores` | `4.35.0` |
+| OpenInference | `openinference.traces` | `0.1.38` |
+| OTLP JSON | `otlp-json.traces` | `0.160.0` |
+| promptfoo | `promptfoo.eval-output` | `0.123.0` |
+| Native evidence bundle | `underwrite.evidence-bundle` | `v1` |
+
+These are bounded payload profiles, not compatibility claims for every export
+from those producers. `project` is an explicit alias of `ingest`.
+
+```sh
+mkdir -p output
+uv run --frozen --no-sync underwrite ingest \
+  --format underwrite.evidence-bundle --version v1 \
+  --file fixtures/examples/measurement/bundle.json --json \
+  > output/observation.json
+uv run --frozen --no-sync underwrite measure \
+  --observation output/observation.json \
+  --policy fixtures/examples/acceptance/policy-quality.json --json \
+  > output/read-quality.json
+uv run --frozen --no-sync underwrite measure \
+  --observation output/observation.json \
+  --policy fixtures/examples/acceptance/policy-latency.json --json \
+  > output/read-latency.json
+```
+
+The native bundle declares `schema_version: underwrite.evidence-bundle.v1` and
+carries readings, source claims, and availability records. An observation keeps
+those source claims separate from the measurement. Measurement requires a
+complete policy identifying inputs, subject, calibration, quorum, and statistical
+thresholds. A successful command exit means the read was produced; inspect the
+read's state before drawing a conclusion.
+
+`--http-body-file FILE` reads an already captured HTTP body from a local file;
+it does not fetch a URL. Optional `--source-ref` and `--source-locator` describe
+the supplied source. When no source reference is given, byte identity supplies
+a content hash, not an independently verified origin. See command `--help` for
+input size and depth limits.
+
+Malformed native input produces a typed error on stderr and no observation on
+stdout. Try a bundle with an empty run identifier:
+
+```sh
+mkdir -p output
+printf '%s\n' '{"schema_version":"underwrite.evidence-bundle.v1","run_id":"","sources":[],"readings":[],"availability":[]}' \
+  > output/malformed-bundle.json
+if uv run --frozen --no-sync underwrite ingest \
+  --format underwrite.evidence-bundle --version v1 \
+  --file output/malformed-bundle.json --json \
+  > output/malformed.stdout 2> output/malformed.stderr; then
+  ingest_exit=0
+else
+  ingest_exit=$?
+fi
+printf 'exit: %s\n' "$ingest_exit"
+wc -c < output/malformed.stdout
+cat output/malformed.stderr
+```
+
+This reports exit `1`, stdout size `0`, and this stderr JSON:
+
+```json
+{"schema":"instrument_error.v1","command":"ingest","code":"INVALID_INPUT","reason":"MALFORMED_EVIDENCE_BUNDLE_PAYLOAD","exit_code":1}
+```
+
+## Classify a candidate
+
+`accept` binds a candidate to declared claims and policy-matched reads. It reports
+whether the supplied evidence supports the requested acceptance basis and retains
+uncertainty or missing measurements in the decision.
+
+```sh
+uv run --frozen --no-sync underwrite accept \
+  --candidate fixtures/examples/acceptance/candidate.json \
+  --claims fixtures/examples/acceptance/claims.json \
+  --read output/read-quality.json \
+  --read output/read-latency.json --json
+```
+
+Repeat `--read` for each required claim. Exit 0 means a classification was
+produced, not approval. This example produces `screened`, requires human review,
+and keeps `merge_authorized` false. The inputs are synthetic local examples;
+the reads above are computed from the supplied bundle and policies.
+
+## Other checks
+
+- `inspect CASE.json --json`: inspect one local artifact manifest and its projection.
+- `check RELEASE.json --json`: check a release manifest's declared evidence linkage.
+- `absence --root DIR --glob '*.json' --min 1 --json`: require a nonempty population.
+- `boundary scan DIR --json`: scan JSON and JSONL strings for configured verdict vocabulary.
+- `drift check --pins-root PINS --siblings-root SOURCES --json`: compare a user-supplied
+  pin registry against local source checkouts.
+- `pins refresh --repo NAME --pins-root PINS --siblings-root SOURCES`: refresh a
+  configured repository's pins from local bytes.
+
+Pin commands are generic utilities; no preconfigured source registry is included.
+Allowlist and exemption evaluation requires an explicit `--now` when applicable.
+Malformed inputs and missing paths remain configuration errors rather than passes.
+Use each command's `--help` for its options and exit behavior. JSON contracts live
+in [contracts/](contracts/); each command family has its own output and error schema.
+
+## Development and license
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the checks and contribution process,
+[SECURITY.md](SECURITY.md) for private vulnerability reporting, and
+[AGENTS.md](AGENTS.md) for technical boundaries. The core package uses only the
+Python standard library; application adapters own local I/O and schema validation.
+
+underwrite is licensed under [Apache-2.0](LICENSE).
+[LICENSING.md](LICENSING.md) records the adapted policy templates' CC licenses.

underwrite-0.0.1/README.md

@@ -0,0 +1,173 @@
+# underwrite
+
+underwrite turns local evaluation artifacts into a common observation, computes
+measurements under an explicit policy, and classifies change candidates against
+declared evidence. It keeps missing evidence visible: `not_measured`,
+`indeterminate`, and `abstained` are distinct outcomes.
+
+It is a Python CLI and library. Artifact inspection checks bytes and declared
+hashes; release checks examine declared linkage and record presence. These checks
+do not establish independent provenance or grant deployment permission.
+
+## Install from source
+
+Requires Python 3.12 or later and [uv](https://docs.astral.sh/uv/).
+
+```sh
+git clone https://github.com/ntts9990/underwrite.git
+cd underwrite
+uv sync --frozen --all-groups
+uv run --frozen --no-sync underwrite --help
+```
+
+The repository includes the `underwrite-core` workspace package. No adjacent
+checkout is needed to install or use the example workflows.
+
+## PyPI release preparation
+
+The functional `0.0.1` release is prepared for `underwrite-core` and `underwrite`;
+publication is not yet confirmed. The existing `underwrite` `0.0.0` entry is a
+reserved placeholder. Use the source installation above until both `0.0.1`
+releases are available. After publication, the planned CLI installation is:
+
+```sh
+uv tool install 'underwrite==0.0.1'
+underwrite --help
+```
+
+Maintainers: create the GitHub environment `pypi`, restrict it to `main`, and
+configure a PyPI GitHub Trusted Publisher on each project with owner `ntts9990`,
+repository `underwrite`, workflow filename `publish.yml`, and environment `pypi`.
+For the new `underwrite-core` project, register a pending publisher under that
+project name; add the publisher to the existing `underwrite` project in its
+Publishing settings. No stored PyPI API token is required.
+
+Once configured, run **Publish PyPI** manually from the `main` branch in
+GitHub Actions. It tests both packages, builds and validates the exact
+distributions, and installs the wheels in a clean
+environment before publishing core and then the application. Only the separate
+publish job receives OIDC permission. Retry with the same artifacts after a
+partial upload; existing registry files must match exactly. A changed artifact
+requires a new version. Confirm both PyPI project releases and a fresh indexed
+installation before describing the release as available.
+
+The workflow follows the official [uv publishing guide](https://docs.astral.sh/uv/guides/package/)
+and [PyPI Trusted Publisher guide](https://docs.pypi.org/trusted-publishers/using-a-publisher/).
+
+## Normalize an artifact
+
+Choose a format and exact supported version explicitly:
+
+| Producer | `--format` | `--version` |
+| --- | --- | --- |
+| DeepEval | `deepeval.test-run` | `4.1.1` |
+| Inspect AI | `inspect.eval-log` | `0.3.263` |
+| Langfuse | `langfuse.observations-v2` or `langfuse.scores` | `4.35.0` |
+| OpenInference | `openinference.traces` | `0.1.38` |
+| OTLP JSON | `otlp-json.traces` | `0.160.0` |
+| promptfoo | `promptfoo.eval-output` | `0.123.0` |
+| Native evidence bundle | `underwrite.evidence-bundle` | `v1` |
+
+These are bounded payload profiles, not compatibility claims for every export
+from those producers. `project` is an explicit alias of `ingest`.
+
+```sh
+mkdir -p output
+uv run --frozen --no-sync underwrite ingest \
+  --format underwrite.evidence-bundle --version v1 \
+  --file fixtures/examples/measurement/bundle.json --json \
+  > output/observation.json
+uv run --frozen --no-sync underwrite measure \
+  --observation output/observation.json \
+  --policy fixtures/examples/acceptance/policy-quality.json --json \
+  > output/read-quality.json
+uv run --frozen --no-sync underwrite measure \
+  --observation output/observation.json \
+  --policy fixtures/examples/acceptance/policy-latency.json --json \
+  > output/read-latency.json
+```
+
+The native bundle declares `schema_version: underwrite.evidence-bundle.v1` and
+carries readings, source claims, and availability records. An observation keeps
+those source claims separate from the measurement. Measurement requires a
+complete policy identifying inputs, subject, calibration, quorum, and statistical
+thresholds. A successful command exit means the read was produced; inspect the
+read's state before drawing a conclusion.
+
+`--http-body-file FILE` reads an already captured HTTP body from a local file;
+it does not fetch a URL. Optional `--source-ref` and `--source-locator` describe
+the supplied source. When no source reference is given, byte identity supplies
+a content hash, not an independently verified origin. See command `--help` for
+input size and depth limits.
+
+Malformed native input produces a typed error on stderr and no observation on
+stdout. Try a bundle with an empty run identifier:
+
+```sh
+mkdir -p output
+printf '%s\n' '{"schema_version":"underwrite.evidence-bundle.v1","run_id":"","sources":[],"readings":[],"availability":[]}' \
+  > output/malformed-bundle.json
+if uv run --frozen --no-sync underwrite ingest \
+  --format underwrite.evidence-bundle --version v1 \
+  --file output/malformed-bundle.json --json \
+  > output/malformed.stdout 2> output/malformed.stderr; then
+  ingest_exit=0
+else
+  ingest_exit=$?
+fi
+printf 'exit: %s\n' "$ingest_exit"
+wc -c < output/malformed.stdout
+cat output/malformed.stderr
+```
+
+This reports exit `1`, stdout size `0`, and this stderr JSON:
+
+```json
+{"schema":"instrument_error.v1","command":"ingest","code":"INVALID_INPUT","reason":"MALFORMED_EVIDENCE_BUNDLE_PAYLOAD","exit_code":1}
+```
+
+## Classify a candidate
+
+`accept` binds a candidate to declared claims and policy-matched reads. It reports
+whether the supplied evidence supports the requested acceptance basis and retains
+uncertainty or missing measurements in the decision.
+
+```sh
+uv run --frozen --no-sync underwrite accept \
+  --candidate fixtures/examples/acceptance/candidate.json \
+  --claims fixtures/examples/acceptance/claims.json \
+  --read output/read-quality.json \
+  --read output/read-latency.json --json
+```
+
+Repeat `--read` for each required claim. Exit 0 means a classification was
+produced, not approval. This example produces `screened`, requires human review,
+and keeps `merge_authorized` false. The inputs are synthetic local examples;
+the reads above are computed from the supplied bundle and policies.
+
+## Other checks
+
+- `inspect CASE.json --json`: inspect one local artifact manifest and its projection.
+- `check RELEASE.json --json`: check a release manifest's declared evidence linkage.
+- `absence --root DIR --glob '*.json' --min 1 --json`: require a nonempty population.
+- `boundary scan DIR --json`: scan JSON and JSONL strings for configured verdict vocabulary.
+- `drift check --pins-root PINS --siblings-root SOURCES --json`: compare a user-supplied
+  pin registry against local source checkouts.
+- `pins refresh --repo NAME --pins-root PINS --siblings-root SOURCES`: refresh a
+  configured repository's pins from local bytes.
+
+Pin commands are generic utilities; no preconfigured source registry is included.
+Allowlist and exemption evaluation requires an explicit `--now` when applicable.
+Malformed inputs and missing paths remain configuration errors rather than passes.
+Use each command's `--help` for its options and exit behavior. JSON contracts live
+in [contracts/](contracts/); each command family has its own output and error schema.
+
+## Development and license
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for the checks and contribution process,
+[SECURITY.md](SECURITY.md) for private vulnerability reporting, and
+[AGENTS.md](AGENTS.md) for technical boundaries. The core package uses only the
+Python standard library; application adapters own local I/O and schema validation.
+
+underwrite is licensed under [Apache-2.0](LICENSE).
+[LICENSING.md](LICENSING.md) records the adapted policy templates' CC licenses.