iqa-org 0.1.0__tar.gz

iqa_org-0.1.0/CHANGELOG.md

@@ -0,0 +1,54 @@
+# Changelog — iqa (Python)
+
+All notable changes to this package are documented here.
+Format: Keep a Changelog; versioning: SemVer.
+
+---
+
+## [0.1.0] — 2026-09-18
+
+Initial public release.
+
+### Added
+
+* **`iqa://` URI codec** (RFC-009 §10.2/§10.3): validate, canonicalise and
+  classify — subject hash forms (8/32/64 lowercase hex) and name forms,
+  **closed-set** enforcement for `organ` (`forge`/`tss`/`gateway`) and
+  `action` (`verify`/`audit`/`attest`/`revoke`), fail-closed rejection of
+  uppercase, userinfo, port, query, fragment, foreign schemes and every
+  structural violation. Field names are snake_case so this output and the
+  JavaScript package's output compare directly against the vectors.
+* **`IQA_ROUTE` derivation** (SPEC/IQA-URI-ATTEST-v1.2.6 §3, decision D1):
+  `SHA-256(ASCII(authority))[0:4]` — pure computation, DNS-free, mirroring the
+  RTTP `ROUTE_SHARD` rule.
+* **Action safety classes** (RFC-009 §11.3) exposed as `action_safe` —
+  omitted/verify SAFE, audit/attest/revoke NOT SAFE.
+* **Sovereign attestation envelope** (`iqa.attest`, optional `[ed25519]`
+  extra): Ed25519, self-certifying `AID = SHA-256(public key)`, domain prefix
+  `iqa-attest-v1`, `ts`/`nonce` inside the signature, 120-second freshness
+  window, claim validation against both closed sets, and a fail-closed
+  verification order — a check that cannot be performed is a failure, never a
+  pass.
+* **59-check self-test** (`python -m iqa.selftest`): 31 conformance + 2
+  RFC 8032 + 22 envelope + 4 zero-dependency; replays the shipped vectors
+  offline.
+* **Conformance vectors** — 32 published checks in four groups (8 positive /
+  18 negative / 5 safety / 1 deterministic envelope), generated by
+  `SPEC/tools/iqa_conformance.py`, shipped inside the wheel, and mirrored
+  byte-identically in the npm package `iqa`.
+
+### Distribution status at this release
+
+| Registry | Name | State |
+|:---|:---|:---|
+| PyPI | **`iqa-org`** | this package — `pip install iqa-org`, `import iqa`. The bare `iqa` is unregistered but blocked by PyPI's typosquatting protection (upload rejected 400, "too similar to an existing project") |
+| npm | **`@aicent/iqa`** | the JavaScript independent implementation — bare name blocked by npm's typosquatting protection, published under the project organization |
+| crates.io | `iqa-org` | held by this project |
+
+### Specification status
+
+The `iqa` URI scheme is submitted to IANA under RFC 7595 (ticket **#1459963**,
+Provisional) and is **under review — not yet registered**. Every artifact in
+this package describes it that way.
+
+[0.1.0]: https://pypi.org/project/iqa/

iqa_org-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+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 2013-2019 Nikolay Kim and Andrew Svetlov
+
+   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.

iqa_org-0.1.0/MANIFEST.in

@@ -0,0 +1,4 @@
+include LICENSE
+include README.md
+include CHANGELOG.md
+recursive-include src/iqa/vectors *.json

iqa_org-0.1.0/PKG-INFO

@@ -0,0 +1,218 @@
+Metadata-Version: 2.4
+Name: iqa-org
+Version: 0.1.0
+Summary: IQA: iqa:// subject-attestation addressing (RFC-009 §10/§11), IQA_ROUTE derivation, and the published conformance vectors that prove an implementation is right
+Author: IQA.ORG Organization
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://iqa.org/
+Project-URL: Specification, https://iqa.org/RFC-009/
+Keywords: iqa,attestation,identity,uri,conformance,ed25519,aicent
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Security :: Cryptography
+Classifier: Topic :: Software Development :: Libraries
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: ed25519
+Requires-Dist: cryptography>=42; extra == "ed25519"
+Provides-Extra: dev
+Requires-Dist: cryptography>=42; extra == "dev"
+Requires-Dist: build; extra == "dev"
+Requires-Dist: twine; extra == "dev"
+Dynamic: license-file
+
+# iqa-org
+
+**Reference implementation of the IQA attestation layer: the `iqa://`
+subject-attestation URI (RFC-009 §10), action safety classes (§11), and the
+self-certifying Ed25519 attestation envelope.**
+
+[RFC-009 §10](https://iqa.org/RFC-009/) · §11 · v1.2.6
+
+---
+
+## Verify it in one command — no trust required
+
+```console
+$ pip install iqa-org
+$ python -m iqa.selftest
+...
+[PASS] all 59 checks passed
+```
+
+That is the point of this package. A specification is worth exactly what an
+independent implementation can reproduce from it — so instead of asking you to
+believe a table of numbers, this ships the vectors and replays them locally:
+
+* **31 conformance checks** — `iqa://` parsing, the two **closed sets**
+  (`organ` / `action` — the deliberate difference from `rttp`, whose verb set
+  is open), fail-closed rejections, §11.3 action safety classes, and the
+  `IQA_ROUTE` derivation.
+* **2 RFC 8032 checks** — the Ed25519 backend is shown to be *standard*
+  Ed25519, not a lookalike, so a failure tells you which half broke.
+* **22 envelope checks** — deterministic-vector reproduction, round-trip,
+  self-certification, freshness, claim validation, and a 14-case tamper matrix
+  where every alteration must be rejected.
+* **4 zero-dependency checks** — a static scan proving the core imports
+  nothing outside the standard library.
+
+Offline. No account. No network. `[PASS]` or it is not.
+
+---
+
+## Install
+
+```console
+pip install iqa-org              # core: zero dependencies, standard library only
+pip install iqa-org[ed25519]     # + sovereign attestation envelopes (Ed25519)
+```
+
+Python 3.9+. No compiled extensions in the core.
+
+The core deliberately has **no dependencies**. A protocol reference that cannot
+be read without resolving a dependency tree is not much of a reference — and an
+air-gapped reviewer should be able to check the claims.
+
+---
+
+## What is in the box
+
+| Module | What it does | Authority |
+|:---|:---|:---|
+| `iqa.iqa_uri` | `iqa://` codec — validate, canonicalise, classify (8/32/64 hex or name subject), enforce the `organ` and `action` **closed sets**, report `action_safe` | RFC-009 §10.1/§10.2/§10.3 |
+| `iqa.iqa_uri.derive_route` | `IQA_ROUTE = SHA-256(ASCII(authority))[0:4]` — pure computation, DNS-free | `SPEC/IQA-URI-ATTEST-v1.2.6.md` §3 |
+| `iqa.attest` | **Sovereign attestation envelope** — Ed25519, self-certifying (`AID = SHA-256(pub)`), domain prefix `iqa-attest-v1`, `ts`/`nonce` inside the signature | `SPEC/IQA-URI-ATTEST-v1.2.6.md` §5 (draft) |
+
+Plus `iqa.vectors` — the published conformance vectors, shipped inside the
+wheel so the self-test works from an installed package with no repository
+checkout.
+
+---
+
+## Quickstart
+
+### Address a standing claim
+
+```python
+from iqa import iqa_uri
+
+parsed = iqa_uri.parse("iqa://3f9a1b2c.gateway.iqa")
+parsed["subject"]        # '3f9a1b2c'   (8-hex routing short form)
+parsed["organ"]          # 'gateway'    (closed set: forge | tss | gateway)
+parsed["action"]         # None         (omitted = standing read, §11.1)
+parsed["action_safe"]    # True         (§11.3)
+parsed["route_hex"]      # '5c378581'   <- pure computation, vector-pinned
+```
+
+Addressing is **DNS-free** (RFC-009 §12 #9): the route fingerprint is derived
+from the authority by SHA-256, so no registry, resolver or network is involved.
+Malformed input is rejected rather than normalised — a case variant is not a
+spelling difference, it is a different string.
+
+### The closed sets — the deliberate difference from `rttp`
+
+```python
+iqa_uri.parse("iqa://3f9a1b2c.gateway.iqa/pulse")
+# IqaUriError: action 'pulse' is outside the closed set — 'pulse' is an rttp verb
+
+iqa_uri.parse("iqa://3f9a1b2c.forgery.iqa")
+# IqaUriError: organ is a closed set (forge | tss | gateway)
+```
+
+### Seal an attestation with your own identity
+
+```python
+from iqa import attest
+
+keypair = attest.generate_keypair()          # nothing is issued to you
+print(keypair["aid_hex"])                    # = SHA-256(public key): your identity
+
+claim = attest.build_claim("iqa://3f9a1b2c.gateway.iqa", "gateway", "radiant")
+envelope = attest.seal(claim, keypair)
+
+ok, reason, aid = attest.verify_envelope(envelope)
+# ok=True — signer identity recovered from the packet itself
+```
+
+The verifier needs **only the envelope**. There is no key directory, no
+credentials to obtain, and no operator who could refuse to issue them. The
+envelope **carries a claim** that an Organ rendered a standing; it does not
+**create** one — verifying an attestation and trusting an attestation are
+different acts (RFC-009 §10.4).
+
+---
+
+## Scope — what this package is not
+
+| | |
+|:---|:---|
+| ✅ **Validation / canonicalisation** | Real, and specified (RFC-009 §10.2 / §10.3). |
+| ✅ **Closed-set enforcement** | Real, and specified (§10.1). |
+| ✅ **IQA_ROUTE derivation** | Real (SPEC §3, decision D1). |
+| ✅ **Action safety classes** | Real, and specified (§11.3). |
+| ✅ **Attestation envelope** | Real, and specified (draft). |
+| ❌ **Dereferencing / resolver service** | Not here. The codec computes; *answering* a standing read is an Organ's job (RFC-009-C §3). |
+| ❌ **Staking & tiers** | ZCMK collateral economics — operator policy, no cryptographic object in this package. |
+| ❌ **Vitality monitoring** | 1200 Hz heartbeats and Homeostasis Scores are telemetry, not codec. |
+| ❌ **Post-quantum Lattice Guard** | RFC-009 §12 #11 schedules it for v1.4.0; no implementation exists. |
+| ❌ **Revocation transport** | §11.3 defines the verb; executing it is not the codec's job. |
+| ❌ **Confidentiality** | Signing is not encryption. |
+
+Unknown revisions, algorithms and malformed input **fail closed** everywhere.
+Nothing in this package is ever accepted because a check could not be performed.
+
+---
+
+## Conformance vectors
+
+`iqa/vectors/iqa-conformance-v1.2.6.json` is generated, not hand-edited. Each
+vector is deterministic: fixed sequence values, fixed timestamp, fixed seed —
+so two implementations either agree byte for byte or they do not. The same
+file ships in the npm package `iqa` (three mirrors, one sha256), and the
+JavaScript side is an **independent** implementation that replays it without
+sharing a line of code with this one.
+
+The vector set is the intended deliverable for third-party certification: pass
+it and you interoperate; fail it and you know exactly which case is wrong,
+without needing to trust the authors.
+
+---
+
+## Naming
+
+| Ecosystem | Name | Status |
+|:---|:---|:---|
+| crates.io | `iqa-org` | held by this project (the Rust crate carries the same name) |
+| PyPI | **`iqa-org`** | **this package** — `pip install iqa-org`, `import iqa` (the import name is unchanged). The bare `iqa` is unregistered but **blocked by PyPI's typosquatting protection** (upload rejected with 400 "too similar to an existing project") — the same class of guard that forced `@aicent/iqa` on npm |
+| npm | **`@aicent/iqa`** | the bare `iqa` name is unregistered but blocked by npm's typosquatting protection (too similar to existing short names) — so the JavaScript side is published under this project's own organization, as `@aicent/rttp` already is. The package name itself is still just `iqa` |
+
+---
+
+## Specification status
+
+* **`iqa` URI scheme** — submitted to IANA under RFC 7595, ticket **#1459963**,
+  Provisional, **under review**. It is **not yet registered** — as of
+  2026-09-18 the IANA "URI Schemes" registry contains no `iqa` entry. Please
+  describe it that way.
+* **URI grammar** — RFC-009 §10.2 (frozen; this package adds no syntax).
+* **Dereference safety** — RFC-009 §11 (closed sets and safety classes).
+* **Attestation envelope** — `SPEC/IQA-URI-ATTEST-v1.2.6.md` §5, a **draft**:
+  the format is implemented and vector-tested, but it is not yet a numbered
+  RFC-009 section.
+
+Where this package and a specification disagree, **the specification wins and
+the package is wrong.** Please report it.
+
+---
+
+## License
+
+Apache-2.0. See `LICENSE`.

iqa_org-0.1.0/README.md

@@ -0,0 +1,187 @@
+# iqa-org
+
+**Reference implementation of the IQA attestation layer: the `iqa://`
+subject-attestation URI (RFC-009 §10), action safety classes (§11), and the
+self-certifying Ed25519 attestation envelope.**
+
+[RFC-009 §10](https://iqa.org/RFC-009/) · §11 · v1.2.6
+
+---
+
+## Verify it in one command — no trust required
+
+```console
+$ pip install iqa-org
+$ python -m iqa.selftest
+...
+[PASS] all 59 checks passed
+```
+
+That is the point of this package. A specification is worth exactly what an
+independent implementation can reproduce from it — so instead of asking you to
+believe a table of numbers, this ships the vectors and replays them locally:
+
+* **31 conformance checks** — `iqa://` parsing, the two **closed sets**
+  (`organ` / `action` — the deliberate difference from `rttp`, whose verb set
+  is open), fail-closed rejections, §11.3 action safety classes, and the
+  `IQA_ROUTE` derivation.
+* **2 RFC 8032 checks** — the Ed25519 backend is shown to be *standard*
+  Ed25519, not a lookalike, so a failure tells you which half broke.
+* **22 envelope checks** — deterministic-vector reproduction, round-trip,
+  self-certification, freshness, claim validation, and a 14-case tamper matrix
+  where every alteration must be rejected.
+* **4 zero-dependency checks** — a static scan proving the core imports
+  nothing outside the standard library.
+
+Offline. No account. No network. `[PASS]` or it is not.
+
+---
+
+## Install
+
+```console
+pip install iqa-org              # core: zero dependencies, standard library only
+pip install iqa-org[ed25519]     # + sovereign attestation envelopes (Ed25519)
+```
+
+Python 3.9+. No compiled extensions in the core.
+
+The core deliberately has **no dependencies**. A protocol reference that cannot
+be read without resolving a dependency tree is not much of a reference — and an
+air-gapped reviewer should be able to check the claims.
+
+---
+
+## What is in the box
+
+| Module | What it does | Authority |
+|:---|:---|:---|
+| `iqa.iqa_uri` | `iqa://` codec — validate, canonicalise, classify (8/32/64 hex or name subject), enforce the `organ` and `action` **closed sets**, report `action_safe` | RFC-009 §10.1/§10.2/§10.3 |
+| `iqa.iqa_uri.derive_route` | `IQA_ROUTE = SHA-256(ASCII(authority))[0:4]` — pure computation, DNS-free | `SPEC/IQA-URI-ATTEST-v1.2.6.md` §3 |
+| `iqa.attest` | **Sovereign attestation envelope** — Ed25519, self-certifying (`AID = SHA-256(pub)`), domain prefix `iqa-attest-v1`, `ts`/`nonce` inside the signature | `SPEC/IQA-URI-ATTEST-v1.2.6.md` §5 (draft) |
+
+Plus `iqa.vectors` — the published conformance vectors, shipped inside the
+wheel so the self-test works from an installed package with no repository
+checkout.
+
+---
+
+## Quickstart
+
+### Address a standing claim
+
+```python
+from iqa import iqa_uri
+
+parsed = iqa_uri.parse("iqa://3f9a1b2c.gateway.iqa")
+parsed["subject"]        # '3f9a1b2c'   (8-hex routing short form)
+parsed["organ"]          # 'gateway'    (closed set: forge | tss | gateway)
+parsed["action"]         # None         (omitted = standing read, §11.1)
+parsed["action_safe"]    # True         (§11.3)
+parsed["route_hex"]      # '5c378581'   <- pure computation, vector-pinned
+```
+
+Addressing is **DNS-free** (RFC-009 §12 #9): the route fingerprint is derived
+from the authority by SHA-256, so no registry, resolver or network is involved.
+Malformed input is rejected rather than normalised — a case variant is not a
+spelling difference, it is a different string.
+
+### The closed sets — the deliberate difference from `rttp`
+
+```python
+iqa_uri.parse("iqa://3f9a1b2c.gateway.iqa/pulse")
+# IqaUriError: action 'pulse' is outside the closed set — 'pulse' is an rttp verb
+
+iqa_uri.parse("iqa://3f9a1b2c.forgery.iqa")
+# IqaUriError: organ is a closed set (forge | tss | gateway)
+```
+
+### Seal an attestation with your own identity
+
+```python
+from iqa import attest
+
+keypair = attest.generate_keypair()          # nothing is issued to you
+print(keypair["aid_hex"])                    # = SHA-256(public key): your identity
+
+claim = attest.build_claim("iqa://3f9a1b2c.gateway.iqa", "gateway", "radiant")
+envelope = attest.seal(claim, keypair)
+
+ok, reason, aid = attest.verify_envelope(envelope)
+# ok=True — signer identity recovered from the packet itself
+```
+
+The verifier needs **only the envelope**. There is no key directory, no
+credentials to obtain, and no operator who could refuse to issue them. The
+envelope **carries a claim** that an Organ rendered a standing; it does not
+**create** one — verifying an attestation and trusting an attestation are
+different acts (RFC-009 §10.4).
+
+---
+
+## Scope — what this package is not
+
+| | |
+|:---|:---|
+| ✅ **Validation / canonicalisation** | Real, and specified (RFC-009 §10.2 / §10.3). |
+| ✅ **Closed-set enforcement** | Real, and specified (§10.1). |
+| ✅ **IQA_ROUTE derivation** | Real (SPEC §3, decision D1). |
+| ✅ **Action safety classes** | Real, and specified (§11.3). |
+| ✅ **Attestation envelope** | Real, and specified (draft). |
+| ❌ **Dereferencing / resolver service** | Not here. The codec computes; *answering* a standing read is an Organ's job (RFC-009-C §3). |
+| ❌ **Staking & tiers** | ZCMK collateral economics — operator policy, no cryptographic object in this package. |
+| ❌ **Vitality monitoring** | 1200 Hz heartbeats and Homeostasis Scores are telemetry, not codec. |
+| ❌ **Post-quantum Lattice Guard** | RFC-009 §12 #11 schedules it for v1.4.0; no implementation exists. |
+| ❌ **Revocation transport** | §11.3 defines the verb; executing it is not the codec's job. |
+| ❌ **Confidentiality** | Signing is not encryption. |
+
+Unknown revisions, algorithms and malformed input **fail closed** everywhere.
+Nothing in this package is ever accepted because a check could not be performed.
+
+---
+
+## Conformance vectors
+
+`iqa/vectors/iqa-conformance-v1.2.6.json` is generated, not hand-edited. Each
+vector is deterministic: fixed sequence values, fixed timestamp, fixed seed —
+so two implementations either agree byte for byte or they do not. The same
+file ships in the npm package `iqa` (three mirrors, one sha256), and the
+JavaScript side is an **independent** implementation that replays it without
+sharing a line of code with this one.
+
+The vector set is the intended deliverable for third-party certification: pass
+it and you interoperate; fail it and you know exactly which case is wrong,
+without needing to trust the authors.
+
+---
+
+## Naming
+
+| Ecosystem | Name | Status |
+|:---|:---|:---|
+| crates.io | `iqa-org` | held by this project (the Rust crate carries the same name) |
+| PyPI | **`iqa-org`** | **this package** — `pip install iqa-org`, `import iqa` (the import name is unchanged). The bare `iqa` is unregistered but **blocked by PyPI's typosquatting protection** (upload rejected with 400 "too similar to an existing project") — the same class of guard that forced `@aicent/iqa` on npm |
+| npm | **`@aicent/iqa`** | the bare `iqa` name is unregistered but blocked by npm's typosquatting protection (too similar to existing short names) — so the JavaScript side is published under this project's own organization, as `@aicent/rttp` already is. The package name itself is still just `iqa` |
+
+---
+
+## Specification status
+
+* **`iqa` URI scheme** — submitted to IANA under RFC 7595, ticket **#1459963**,
+  Provisional, **under review**. It is **not yet registered** — as of
+  2026-09-18 the IANA "URI Schemes" registry contains no `iqa` entry. Please
+  describe it that way.
+* **URI grammar** — RFC-009 §10.2 (frozen; this package adds no syntax).
+* **Dereference safety** — RFC-009 §11 (closed sets and safety classes).
+* **Attestation envelope** — `SPEC/IQA-URI-ATTEST-v1.2.6.md` §5, a **draft**:
+  the format is implemented and vector-tested, but it is not yet a numbered
+  RFC-009 section.
+
+Where this package and a specification disagree, **the specification wins and
+the package is wrong.** Please report it.
+
+---
+
+## License
+
+Apache-2.0. See `LICENSE`.