asexec 0.3.14__tar.gz

asexec-0.3.14/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.

asexec-0.3.14/PKG-INFO

@@ -0,0 +1,271 @@
+Metadata-Version: 2.4
+Name: asexec
+Version: 0.3.14
+Summary: Pre-registration & notarization primitive for AI evaluations — commit-then-reveal receipts so silence becomes evidence
+Keywords: ai-safety,evaluations,pre-registration,attestation,cryptography,notarization
+Author: Luke Whitestone
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security :: Cryptography
+Requires-Dist: pynacl>=1.5
+Requires-Dist: py-ecc>=6.0
+Requires-Dist: pydantic>=2
+Requires-Dist: blake3>=0.3 ; extra == 'blake3'
+Requires-Python: >=3.11
+Project-URL: Homepage, https://github.com/lwhitestone/asexec
+Project-URL: Issues, https://github.com/lwhitestone/asexec/issues
+Provides-Extra: blake3
+Description-Content-Type: text/markdown
+
+# asexec - AsExecuted
+
+**Pre-registered trials for AI executions.** A local-first, pseudonymous, offline-verifiable
+cryptographic primitive: a practitioner commits to running a test *before* the results are
+known, then publishes tamper-evident, independently-verifiable receipts of what actually
+happened, so that silence after public commitment becomes visible evidence of
+non-disclosure.
+
+It is the "as executed" counterpart to pre-registration ("as predicted"), borrowing the
+commit-then-reveal mechanism from clinical-trial pre-registration and applying it to the
+selective-disclosure problem in AI safety.
+
+`asexec` is a primitive, not a platform. It offers a signing/verification library and a thin CLI.
+There is no hosted service, no CA, no leaderboard, etc, in the core product. Publish the files
+wherever you like according to how you wish to disclose.
+
+---
+
+## What does `asexec` prove?
+
+What a particular execution cycle's manifest proves is up to the practitioner (who can
+choose what to disclose) and the verifier (who can choose what to check). Proof comes
+in the form of `asexec verify` providing a code regarding the checks applied.
+
+**`asexec` can prove:**
+- A manifest (pre-registration or post-registration) was not altered after signing.
+- A post-registration references a specific prior pre-registration, and a sequence wasn't
+  silently truncated/reordered (a `prev_hash` chain). *(Partially enforced in 0.3.x — see
+  [Known issues](#known-issues-03x-alpha).)*
+- A declared disclosure deadline (`due`) did not expire prior to post-registration (rendered
+  as an explicit state `fulfilled`/`open`/`elapsed-no-receipt`/`notarization-only`). *(Not
+  yet enforced in 0.3.x — see [Known issues](#known-issues-03x-alpha).)*
+- A manifest was created no earlier than a public moment (floor "freshness" check, offered by
+  `drand`).
+- A manifest was created no later than time T (ceiling "witness" check, offered by `Roughtime`;
+  a signature-witness, not proof-of-work).
+
+**`asexec` does not prove**:
+- Provenance. Content hashes prove a transcript wasn't altered; they do not prove it is the
+  output of the named harness+model (asserted by the signer, not re-executed).
+- Completeness. It renders only the manifests you give it; it cannot prove a lab pre-registered
+  every eval it should have (selective pre-registration). However, just like practitioners are not
+  forced to `asexec prereg` all their testing, verifiers are not forced to trust results that were
+  telegraphed less than they could have been. It is a signal of good faith to pre-register as much
+  as you can!
+- Qualities of the science of evals, including eval quality, elicitation rigor, sandbagging, etc.
+  `asexec` aims to make the process of AI testing auditable, but does not make claims about the
+  science itself.
+- Anti-forgery of verify codes. The code is a summary of a computation, not a certificate. It is
+  meaningful to verifiers only when produced from the registration files. In other words, don't
+  blindly trust a verify code handed to you; see if you can reproduce it!
+
+---
+
+## Install
+
+```bash
+pip install asexec # ed25519 (PyNaCl) + BLS verification for drand (py_ecc)
+```
+
+## Quickstart (the full commit-then-reveal cycle)
+
+```bash
+# 1. Practitioner, one-time: generate a pseudonymous keypair (no CA, no registration)
+asexec keygen --out lab.key
+
+# 2. Practitioner, BEFORE the run: pre-register the target
+asexec prereg --key lab.key \
+    --subject ./harness \
+    --target "claude-opus-4-8 via the anthropic API" \
+    --due 2026-08-30T00:00:00Z \
+    --declaration "all runs of this harness against this model, in full" \
+    --out preregistration.json
+
+# 3. Practitioner, AFTER each run: post-register a receipt of the inputs
+asexec postreg --key lab.key --fulfills preregistration.json \
+    --subject ./transcript.txt ./harness \
+    --out postregistration.json
+
+# 4. Any verifier, anytime: verify the cycle and render the commitment state.
+#    --tests names exactly which checks to run; 'BDR' (sig + keyid) is required.
+asexec verify preregistration.json postregistration.json \
+    --tests BDR,content,chain,keyconsist --artifacts .
+```
+
+For a detailed look at parameters and options, see: `asexec --help`.
+
+### The verify code (what step 4 produces)
+
+`verify` runs the tests you name and prints one canonical code, e.g.:
+
+```
+asexec-verify/1 BDR=PASS chain=PASS content=PASS keyconsist=PASS
+```
+
+Grammar (`asexec-verify/1` versions the code format): the literal prefix, then one
+`name=RESULT` token per requested test (`RESULT ∈ {PASS, FAIL}`), sorted alphabetically,
+single-space delimited. The same result set is byte-identical everywhere.
+
+- You declare your appetite. `--tests` is required and must include `BDR` (bedrock - the
+  mandatory minimum: signature + keyid). Everything else is opt-in: `content` (subject
+  digests vs. `--artifacts`), `chain` (`prev_hash` integrity), `keyconsist` (postregs share
+  the prereg's key), `floor` (drand freshness), `ceiling` (Roughtime witness).
+- Named, not scored, so it's forward-compatible. Because the code names which tests
+  ran, adding a test in a later version can never change the meaning of an older code. A code
+  means exactly one thing, permanently.
+- A requested test that applies nowhere is `FAIL`, never a silent omission (e.g.
+  `--tests BDR,ceiling` on manifests with no ceiling -> `ceiling=FAIL`).
+- The code is not a certificate. Real verification comes from the verifier running the tool
+  against the files and get the code.
+
+## Identity (optional domain control check, no CA)
+
+```bash
+# A domain owner asserts which keys speak for it:
+asexec identity emit --key lab.key --domain lab.example --out asexec.json
+#   -> publish at https://lab.example/.well-known/asexec.json
+
+# Anyone checks the binding for a match (point-in-time; a domain can rotate keys):
+asexec identity match --domain lab.example --key lab.key
+#   -> GET https://lab.example/.well-known/asexec.json
+#   -> returns bound==True iff specified key exists there.
+```
+
+## Network requirements
+
+Most `asexec` functionality is fully offline, which serves to drastically reduce the trust
+surface. This includes all `asexec verify` operations, which are 100% offline by design;
+everything needed to perform a verification is baked-in to the prereg/postreg manifests.
+
+There are a few opt-in registration paths that use a network connection:
+
+- `prereg/postreg --floor`: Fetches a distributed randomness beacon round from `api.drand.sh`
+  (or a fallback) at sign-time.
+- `prereg/postreg --ceiling`: Makes a UDP socket call (with server-list fallbacks) to a
+  Roughtime server at sign-time.
+
+The `asexec identity` check loop is also network-dependent, as it is explicitly a domain-
+ownership check. It exists outside registration verification as an opt-in helper.
+
+## Manifest at a glance
+
+Bespoke signed JSON, signed over a DSSE-style PAE input (borrows in-toto field names, not the
+tooling). The bedrock (mandatory) set is deliberately small - the fields whose absence
+would break verifiability of commitment -> fulfillment/gap:
+
+- semantic: `target` (what was committed to - plain text or structured JSON). This is the
+  only mandatory claim.
+- structural: the format frame - `schema_version`, `predicateType`, `phase`
+  (`prereg` | `postreg`).
+
+Everything else is individually optional: `due` (the disclosure deadline — a commitment
+without one simply stays `open`), `declaration` (plain-language or structured commitment
+text), `subject` + `hash_alg` (conditionally paired - `hash_alg` is required iff a
+`subject` is present; a pre-registration may commit to a target before any harness exists to
+hash), `anchor.floor` (drand, opt-in via `--floor`), `identity`, `provenance` +
+`repro_recipe`, free-form `notes`. Specificity is a trust gradient the reader prices.
+
+The ceiling witness (Roughtime) lives at the envelope level, beside `payload` and
+`signature` - not inside the signed body, because its nonce is the body's own hash
+(`ref(payload)`), which can't be embedded in the thing it hashes. It is self-authenticated by
+the witness signature and binds to the manifest via `nonce == ref(payload)`. This is a purposeful
+asymmetry between floor and ceiling, because the proof of floor requires a piece of information
+to be embedded in the manifest, while the ceiling proof requires the payload to be referenced
+by an external witness.
+
+## Prior art and related projects 
+
+AsPredicted/OSF pre-registration, ClinicalTrials.gov + the FDAAA TrialsTracker,
+OpenTimestamps, in-toto/DSSE, drand/League of Entropy.
+
+## Development and Releases
+
+Local setup, checks, CI, and the tag-triggered release pipeline (TestPyPI, then PyPI after
+manual approval) are documented in [`docs/DEVELOPMENT.md`](./docs/DEVELOPMENT.md).
+
+Quick start:
+
+```bash
+scripts/dev-setup.sh   # one-time setup
+scripts/check.sh       # lint + format check + tests
+```
+
+## Author
+
+Designed by Luke Whitestone. Check out my other projects at: **[lukewhitest.one](https://lukewhitest.one/)**.
+
+## Status
+
+Currently: **0.3.x - alpha.** Realigns the vocabulary and hardens the types (breaking, no back-compat):
+`prereg`/`postreg` commands + phases, a free-form `target` (the only mandatory claim), an
+optional `due` deadline + `declaration`, opt-in drand `--floor`, the `BDR` bedrock code
+token, and Pydantic-typed manifest construction. Builds on 0.2.0's schema rebalance + typed
+`anchor.floor` (drand) / external-witness `ceiling` (Roughtime) + canonical
+`asexec-verify/1` code. See [`ROADMAP.md`](./ROADMAP.md) for the version-keyed backlog —
+including later items (per-key public index, re-execution/determinism mode) and what is
+explicitly not scheduled (hosted transparency log, identity binding/CA).
+
+> Ceiling — status: the Roughtime verification protocol (delegation chain, Merkle path,
+> validity window) is fully implemented and offline-verifiable. Long-term keys for four public
+> IETF-Roughtime servers are pinned from the official ecosystem list, and the wire format is
+> reconciled against a live `int08h-Roughtime` capture baked as an offline fixture. The
+> other three servers weren't reachable during capture (UDP egress, not a known format
+> mismatch), so end-to-end interop is proven for int08h and expected-but-unproven for the
+> rest. `--ceiling` fetch fails safe if a server's variant differs.
+
+> **No backward-compatibility guarantee before `1.0.0`.** This is pre-1.0 alpha: any release
+> may change the manifest schema, the signed-byte format, the verifier output, or the CLI
+> without a migration path — manifests signed by an older build may stop verifying against a
+> newer one. (0.2.0 rebalanced the schema in a breaking way by design.) Stability begins at
+> `1.0.0`, which is neither defined nor planned yet.
+
+## Known issues (0.3.x alpha)
+
+The following were confirmed against 0.3.11 and are scheduled for the 0.3.14 soundness patch
+(format-level fixes in 0.4.0). See [`ROADMAP.md`](./ROADMAP.md). Until then, treat
+`asexec verify` output with these caveats:
+
+**Commitment state and chain**
+- A post-registration signed by *any* key - or with an *invalid* signature - causes its
+  pre-registration to render `fulfilled`. Always request `keyconsist` and require `BDR=PASS`
+  before trusting a `fulfilled` state.
+- `chain` does not reject a forked `prev_hash` chain (two receipts pointing at the same
+  predecessor), and dropping the *last* receipt(s) of a chain is undetectable.
+- Timeliness is not checked: a post-registration created after `due` still renders
+  `fulfilled`.
+- A `due` without a timezone is interpreted in the verifier's local timezone, and an
+  unparseable `due` silently renders `open`.
+
+**Input handling**
+- Duplicate JSON keys in a manifest are accepted (last value wins), so a file can display a
+  different value than the one that was verified.
+- `BDR` checks the signature only; any signed JSON object passes, whether or not it is a
+  well-formed asexec manifest.
+- Malformed input (e.g. invalid JSON) crashes `verify` instead of producing `FAIL`.
+- `content` resolves subject names containing `../` or absolute paths outside `--artifacts`.
+- Directory hashing (v1) is ambiguous on POSIX: a filename containing a newline can make two
+  different trees hash identically. Symlinks are skipped silently.
+
+**Signing-side**
+- `keygen --out` overwrites an existing key file without warning.
+- If a `--floor`/`--ceiling` fetch fails, the manifest is still signed (with a warning) without
+  the requested anchor.
+- A mistyped `--fulfills` path is stored verbatim as the reference instead of erroring.
+
+## License
+
+Apache-2.0.