aot-ev1 0.1.0__tar.gz

aot_ev1-0.1.0/DECISIONS_LOG.md

@@ -0,0 +1,60 @@
+# DECISIONS_LOG
+
+Format bytes are defined by `SPEC.md`; this file records only the
+interpretations needed to implement v1 without changing those bytes.
+
+## D1 — EIP-712 projection of the payload (SPEC §4)
+
+EIP-712 has no null and no arbitrary JSON type, so the typed-data message
+projects the payload as follows (both issuer and auditor sign the same
+projection, domain `AOT-EV1` / `1` / `chainId`, no `verifyingContract`):
+
+| payload field | EIP-712 type | null encoding |
+|---|---|---|
+| `v` | `string` | — |
+| `issuer` | `Identity` | — |
+| `auditor` | `Identity` | zero `bytes32` struct hash |
+| `subject` | `Subject` | — |
+| `claims` | `bytes32` | — (`keccak256(canonical_bytes(claims))`) |
+| `valid_from` | `uint64` | — |
+| `valid_until` | `uint64` | `null` → `0` (SPEC forbids `0`, so no collision) |
+| `nonce` | `string` | — |
+| `prev_evidence_hash` | `string` | zero `bytes32` |
+| `revocation` | `Revocation` | zero `bytes32` struct hash |
+| `Identity.display`, `Subject.uri` | `string` | zero `bytes32` (distinct from `""`) |
+
+The mapping is injective for every value the payload schema permits: `null`
+maps to the all-zero `bytes32`, which no `keccak256`/struct hash can produce,
+and `valid_until = 0` is rejected by SPEC §2. `claims` is committed as the
+keccak of its canonical bytes because EIP-712 cannot encode arbitrary JSON.
+
+## D2 — `chainId` is a verifier input (SPEC §4, §6)
+
+SPEC fixes `chainId` in the signing domain but does not store it in the
+payload or manifest. Adding a field would change the v1 bytes, so `aotev`
+takes `--chain-id` (default `1`) at sign and verify time. EIP-712 bundles
+signed for another chain must be verified with that `--chain-id`.
+
+## D3 — Deterministic `created_at`
+
+`manifest.created_at` is chosen by the caller (`--created-at`); the default
+is `payload.valid_from`. This keeps `aotev bundle` reproducible: two runs
+over the same input produce the same file (a wall-clock default would break
+the determinism requirement).
+
+## D4 — Chain step compares evidence hashes
+
+Step 12 reads the previous bundle's canonical `payload.json`, recomputes its
+`evidence_hash` and compares it with `prev_evidence_hash`. Full re-verification
+of the predecessor is left to a separate `aotev verify <prev>` invocation; the
+current bundle never depends on a neighbour to be verifiable.
+
+## D5 — Status precedence and entry limits
+
+* Revocation is checked before expiry, so a payload that is both expired and
+  revoked reports `revoked`.
+* Unpack limits (≤ 32 records, ≤ 8 MiB, ASCII names, no traversal) are
+  enforced during step 2 and report `E_ENTRY_NAME`; SPEC does not define a
+  separate code for them.
+* Exit-code precedence follows SPEC §8: steps 1–10 → `2`, chain → `4`,
+  expired/revoked → `3`, valid → `0`.

aot_ev1-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

aot_ev1-0.1.0/MANIFEST.in

@@ -0,0 +1,9 @@
+include LICENSE
+include README.md
+include SPEC.md
+include DECISIONS_LOG.md
+
+recursive-include aot_ev1/schema *.json
+recursive-include schema *.json
+recursive-include vectors *.json *.md
+recursive-include tests *.py

aot_ev1-0.1.0/PKG-INFO

@@ -0,0 +1,62 @@
+Metadata-Version: 2.4
+Name: aot-ev1
+Version: 0.1.0
+Summary: AOT-EV1 — deterministic evidence layer for the ERC-8325 evidenceHash slot
+Author-email: AOTrust <legal@aotrust.link>
+License-Expression: Apache-2.0
+Keywords: evidence,attestation,erc-8325,jcs,ed25519,provenance
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pynacl>=1.5
+Provides-Extra: evm
+Requires-Dist: eth-account>=0.13; extra == "evm"
+Provides-Extra: anchor
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: build>=1.2; extra == "dev"
+Dynamic: license-file
+
+# AOT-EV1
+
+Deterministic evidence layer for the `evidenceHash` slot of ERC-8325: **who** asserted something,
+**what exactly**, and **until when** it holds — verifiable offline, years later.
+
+- `canonical` — JCS (RFC 8785 subset): no floats, ASCII keys, byte-identical output.
+- `sign` — strict Ed25519 (mandatory) + EIP-712 (optional `[evm]`).
+- `verify` — 12 offline checks, one error code per check, no network.
+- `bundle` — deterministic `.aotev.zip` (stored, fixed order, fixed timestamps).
+
+Core is independent of any service; anchoring is an optional extra (`[anchor]`).
+
+## Usage
+
+```bash
+aotev canonical payload.json          # canonical bytes + evidence_hash
+aotev sign --payload payload.json --issuer-key <seed-hex> --out signed/
+aotev bundle signed/ -o evidence.aotev.zip
+aotev verify evidence.aotev.zip --now 1750000000
+aotev verify evidence.aotev.zip --chain previous.aotev.zip
+aotev inspect evidence.aotev.zip
+aotev inspect --types
+```
+
+Exit codes: `0` valid, `2` broken (steps 1–10), `3` signature-valid but
+expired/revoked, `4` chain error. Verification is fully offline; without
+`--chain` the status is `chain: unverified` and that is not an error.
+
+EIP-712 bundles need a `chainId` for verification. The bundle format does not
+carry it (SPEC §4 fixes only `name`/`version`/`chainId` in the domain), so
+`aotev` uses `--chain-id` with a default of `1`; pass the value used at signing
+time for other chains.
+
+Deterministic defaults: `created_at` defaults to `payload.valid_from`, so two
+`bundle` runs over the same input produce the same file.
+
+Test-only keys live in `tests/helpers.py` and `vectors/`; they are never used
+in production. Conformance vectors are regenerated with
+`PYTHONPATH=. python tests/test_vectors.py --write`.
+
+Status: **v0.1 in development**. Contract: [SPEC.md](SPEC.md).
+
+License: Apache-2.0. Maintained by the AOTrust project (legal@aotrust.link).

aot_ev1-0.1.0/README.md

@@ -0,0 +1,43 @@
+# AOT-EV1
+
+Deterministic evidence layer for the `evidenceHash` slot of ERC-8325: **who** asserted something,
+**what exactly**, and **until when** it holds — verifiable offline, years later.
+
+- `canonical` — JCS (RFC 8785 subset): no floats, ASCII keys, byte-identical output.
+- `sign` — strict Ed25519 (mandatory) + EIP-712 (optional `[evm]`).
+- `verify` — 12 offline checks, one error code per check, no network.
+- `bundle` — deterministic `.aotev.zip` (stored, fixed order, fixed timestamps).
+
+Core is independent of any service; anchoring is an optional extra (`[anchor]`).
+
+## Usage
+
+```bash
+aotev canonical payload.json          # canonical bytes + evidence_hash
+aotev sign --payload payload.json --issuer-key <seed-hex> --out signed/
+aotev bundle signed/ -o evidence.aotev.zip
+aotev verify evidence.aotev.zip --now 1750000000
+aotev verify evidence.aotev.zip --chain previous.aotev.zip
+aotev inspect evidence.aotev.zip
+aotev inspect --types
+```
+
+Exit codes: `0` valid, `2` broken (steps 1–10), `3` signature-valid but
+expired/revoked, `4` chain error. Verification is fully offline; without
+`--chain` the status is `chain: unverified` and that is not an error.
+
+EIP-712 bundles need a `chainId` for verification. The bundle format does not
+carry it (SPEC §4 fixes only `name`/`version`/`chainId` in the domain), so
+`aotev` uses `--chain-id` with a default of `1`; pass the value used at signing
+time for other chains.
+
+Deterministic defaults: `created_at` defaults to `payload.valid_from`, so two
+`bundle` runs over the same input produce the same file.
+
+Test-only keys live in `tests/helpers.py` and `vectors/`; they are never used
+in production. Conformance vectors are regenerated with
+`PYTHONPATH=. python tests/test_vectors.py --write`.
+
+Status: **v0.1 in development**. Contract: [SPEC.md](SPEC.md).
+
+License: Apache-2.0. Maintained by the AOTrust project (legal@aotrust.link).

aot_ev1-0.1.0/SPEC.md

@@ -0,0 +1,127 @@
+# AOT-EV1 — спецификация формата доказательства (v0.1, черновик)
+
+Статус: контракт для реализации MVP. Менять только через запись в DECISIONS_LOG.
+Слой доказательств под слот `evidenceHash` стандарта ERC-8325: кто заявил, что именно, и до какого срока это верно.
+
+## 1. Единицы формата
+
+- `payload` — JSON-объект (см. §2). Хранится в бандле **ровно в канонических байтах** (§3).
+- `evidence_hash` — 32 байта: `sha256(b"AOT-EV1" ‖ canonical_bytes)` (конкатенация без разделителя;
+  канонический JSON всегда начинается с `{`, поэтому префикс однозначно отделён).
+- `bundle` — zip-файл `<evidence_hash-в-hex>.aotev.zip` (§6).
+- `bundle_hash` — 32 байта, привязка содержимого бандла (§7).
+
+## 2. Payload
+
+| Поле | Тип | Обяз. | Правила |
+|---|---|---|---|
+| `v` | str | да | ровно `"1"` |
+| `issuer` | Identity | да | кто заявил |
+| `auditor` | Identity \| null | да (может быть null) | кто независимо подтвердил |
+| `subject` | Subject | да | о чём заявление |
+| `claims` | object | да (может быть пустым) | произвольные значения без float |
+| `valid_from` | int | да | unix-секунды, `≥ 0` |
+| `valid_until` | int \| null | да | unix-секунды, `> valid_from` либо null |
+| `nonce` | str | да | 64 hex-символа (32 байта), криптослучайный |
+| `prev_evidence_hash` | str \| null | да | 64 hex или null (цепочка версий) |
+| `revocation` | object \| null | да | `{"revoked_at": int, "reason": str}` или null |
+
+`Identity = {"scheme": "ed25519"|"eip712", "key_id": str, "display": str|null}`
+— для `ed25519` `key_id` = 64 hex (сырой публичный ключ); для `eip712` — адрес EIP-55 (42 символа).
+
+`Subject = {"type": str, "hash_alg": "sha256", "hash": str, "uri": str|null}`
+— `hash` = 64 hex; `uri` — необязательная ссылка на документ.
+
+**Запрещено:** float в любом месте; числа по модулю > 2^53−1; ключи объектов вне `[A-Za-z0-9_.-]`;
+дубликаты ключей; строки с одиночными суррогатными кодами.
+
+## 3. Канонизация (JCS RFC 8785, подмножество)
+
+- Ключи объектов сортируются по код-поинтам (при ограничении §2 это совпадает с UTF-16-порядком JCS).
+- Сериализация: `,` и `:` без пробелов; строки — `ensure_ascii=True`; `\uXXXX` в нижнем регистре hex;
+  экранируются только `"`, `\` и управляющие `< 0x20` (`\b \f \n \r \t`, иначе `\u00XX`).
+- Целые — без ведущих нулей, без `+`, `-0` недопустим.
+- Пустой объект `{}`, пустой массив `[]`.
+- Инвариант: `canonical(x)` дважды → идентичные байты; кодировка UTF-8, NFC не применяется (вход уже ASCII-ключи).
+
+## 4. Подписи
+
+| Роль | Схема | Что подписывается |
+|---|---|---|
+| issuer | ed25519 | `b"AOT-EV1-sig-v1\x00" ‖ evidence_hash` |
+| auditor | ed25519 | `b"AOT-EV1-aud-v1\x00" ‖ evidence_hash` |
+| issuer / auditor | eip712 | typed data: домен `{"name":"AOT-EV1","version":"1","chainId":<int>}` (поле `verifyingContract` **не включается**), тип `Evidence` = поля payload, вложенные типы `Identity` и `Subject`; сообщение — сам payload |
+
+Проверка Ed25519 — модуль `aot_ev1.ed25519_strict.verify_strict` (S<L, каноничность R и ключа, запрет
+8 точек малого порядка). Схема из `issuer.scheme` обязана совпадать с фактически проверенной.
+`auditor.key_id` обязан отличаться от `issuer.key_id`.
+
+## 5. Срок и отзыв
+
+- `valid_until` входит в подписанное сообщение: продлить нельзя, не выпустив новый бандл.
+- `revocation` — тоже внутри подписанного payload; отзыв постфактум = новый бандл с тем же `subject`
+  и `prev_evidence_hash`, указывающим на отзываемый.
+- Верификатор считает просроченный или отозванный бандл **валидным по подписи**, но со статусом
+  `expired` / `revoked` (код выхода 3), а не «битым».
+
+## 6. Бандл
+
+Записи (порядок фиксирован, `manifest.json` первым, остальные — по возрастанию имени):
+
+```
+manifest.json
+payload.json                      # ровно канонические байты
+signatures/issuer.ed25519         # 64 байта
+signatures/issuer.eip712          # 65 байт (r||s||v), если схема eip712
+signatures/auditor.ed25519        # если есть аудитор
+signatures/auditor.eip712         # если есть
+```
+
+`manifest.json` (тоже канонические байты):
+
+```json
+{"v":"1","created_at":<int>,"evidence_hash":"<hex>","payload_sha256":"<hex>",
+ "entries":[{"name":"payload.json","sha256":"<hex>","size":<int>}, …],
+ "signatures":[{"role":"issuer","scheme":"ed25519","key_id":"<hex>","file":"signatures/issuer.ed25519"}, …],
+ "bundle_hash":"<hex>"}
+```
+
+Zip: `ZIP_STORED`, `date_time=(1980,1,1,0,0,0)`, `create_system=0`, `external_attr=0o100644<<16`,
+`flag_bits=0`, без extra-полей и комментариев, имена — ASCII. Пределы: ≤ 32 записи, ≤ 8 МиБ распакованных.
+
+## 7. bundle_hash
+
+```
+digest_i = sha256(content_i)
+bundle_hash = sha256( b"".join(name_i.encode() + b"\x00" + digest_i for name_i in sorted(names)) )
+```
+
+Порядок — по возрастанию имён, разделителей между записями нет (длина имени известна из строки).
+
+## 8. Верификация (12 шагов)
+
+| # | Проверка | Код ошибки |
+|---|---|---|
+| 1 | файл открывается как zip | `E_BUNDLE_NOT_ZIP` |
+| 2 | нет дублей имён, нет `..`/абсолютных путей, только ASCII | `E_ENTRY_NAME` |
+| 3 | `manifest.json` в корне ровно один; все записи перечислены | `E_MANIFEST` |
+| 4 | `bundle_hash` пересчитан по §7 и совпал | `E_BUNDLE_HASH` |
+| 5 | sha256 каждой записи совпал с манифестом | `E_ENTRY_HASH` |
+| 6 | `payload.json` == канонические байты разобранного payload | `E_CANONICAL` |
+| 7 | payload проходит JSON Schema (`schema/aot-ev1.schema.json`) | `E_SCHEMA` |
+| 8 | `evidence_hash` пересчитан по §1 и совпал с манифестом | `E_EVIDENCE_HASH` |
+| 9 | подпись issuer валидна для своей схемы | `E_SIGNATURE` |
+| 10 | подпись auditor валидна и ключ ≠ issuer | `E_AUDITOR` |
+| 11 | `valid_from ≤ now ≤ valid_until` (если задан) и `revocation == null` | `E_EXPIRED` / `E_REVOKED` |
+| 12 | если задан `--chain <prev.aotev.zip>`: `prev_evidence_hash` == его `evidence_hash` | `E_CHAIN` |
+
+Без `--chain` шаг 12 пропускается, статус `chain: unverified` (это **не** ошибка).
+Сеть не используется ни на одном шаге.
+
+Коды выхода CLI: `0` валиден, `2` битый (шаги 1–10), `3` валиден по подписи, но просрочен/отозван,
+`4` ошибка цепочки.
+
+## 9. Версионирование
+
+`v` в payload и в манифесте — целое в строке. Любое изменение байтов формата = `v2` и новый
+`evidence_hash`-домен (`b"AOT-EV2"`). Векторы версии 1 остаются в репозитории навсегда.

aot_ev1-0.1.0/aot_ev1/__init__.py

@@ -0,0 +1,4 @@
+"""AOT-EV1 — deterministic evidence layer (see SPEC.md)."""
+
+__version__ = "0.1.0"
+__all__ = ["__version__"]

aot_ev1-0.1.0/aot_ev1/anchor.py

@@ -0,0 +1,16 @@
+"""Optional anchoring hook — optional, not part of core.
+
+AOT-EV1 deliberately ships without any anchoring (no BTC timestamps, no
+network calls). A future extra may implement :func:`anchor_bundle`; until
+then it is an explicit stub so callers fail loudly instead of assuming that
+an evidence bundle has been anchored.
+"""
+
+from __future__ import annotations
+
+from typing import Any, NoReturn
+
+
+def anchor_bundle(*args: Any, **kwargs: Any) -> NoReturn:
+    """Anchor a bundle (optional, not part of core) — not implemented."""
+    raise NotImplementedError("optional, not part of core")