celatim 0.1.0__tar.gz

celatim-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.

celatim-0.1.0/PKG-INFO

@@ -0,0 +1,265 @@
+Metadata-Version: 2.4
+Name: celatim
+Version: 0.1.0
+Summary: Typed covert-channel research, measurement, and endpoint tooling for IETF protocol fields.
+Keywords: covert-channels,network-measurement,network-protocols,privacy,steganography
+Author: Michael Bommarito
+Author-email: Michael Bommarito <michael.bommarito@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Dist: cryptography>=46.0.3 ; extra == 'crypto'
+Requires-Dist: aioquic>=1.3.0 ; extra == 'daemon'
+Requires-Dist: h2>=4.3.0 ; extra == 'daemon'
+Requires-Dist: dnspython>=2.8.0 ; extra == 'dns'
+Requires-Dist: aiocoap>=0.4.12 ; extra == 'iot'
+Requires-Dist: paho-mqtt>=2.1.0 ; extra == 'iot'
+Requires-Dist: scapy>=2.6.1 ; extra == 'packet'
+Requires-Dist: websockets>=13.0 ; extra == 'realtime'
+Requires-Dist: paramiko>=3.5.0 ; extra == 'ssh'
+Requires-Python: >=3.14
+Project-URL: Homepage, https://github.com/mjbommar/celatim
+Project-URL: Issues, https://github.com/mjbommar/celatim/issues
+Project-URL: Repository, https://github.com/mjbommar/celatim.git
+Provides-Extra: crypto
+Provides-Extra: daemon
+Provides-Extra: dns
+Provides-Extra: iot
+Provides-Extra: packet
+Provides-Extra: realtime
+Provides-Extra: ssh
+Description-Content-Type: text/markdown
+
+# Celatim
+
+Celatim is a typed Python 3.14+ toolkit for reproducible research on covert channels
+and steganographic carriers in IETF protocol fields. It provides channel codecs,
+protocol data-unit implementations, controlled endpoint transports, structural capacity
+models, detector and scrub guidance, scenario execution, and evidence artifacts from one
+distribution and one import namespace.
+
+The project accompanies a survey and measurement paper. Its channel and defensive
+implementations are published together so researchers can reproduce the measurements,
+inspect assumptions, and evaluate both communication and normalization behavior.
+
+Use Celatim only in controlled environments and on systems and networks you are
+authorized to test.
+
+## Requirements
+
+- CPython 3.14 or newer.
+- Linux for AF_PACKET, network-namespace, tcpdump, and QEMU/TAP workflows.
+- No optional protocol stack is imported by the base package.
+
+## Installation
+
+```bash
+python -m pip install celatim
+celatim --help
+```
+
+The wheel installs one primary command, `celatim`, plus four deterministic report
+generators from the same codebase:
+
+- `celatim-paper-figures`
+- `celatim-paper-macros`
+- `celatim-paper-tables`
+- `celatim-support-matrix`
+
+## Install profiles
+
+Optional dependencies are grouped by capability:
+
+| Extra | Capability |
+|---|---|
+| `celatim[packet]` | Scapy packet construction, parsing, and pcap integration |
+| `celatim[crypto]` | ECDSA and RSA-PSS transcript experiments |
+| `celatim[daemon]` | hyper-h2 and aioquic production-stack paths |
+| `celatim[dns]` | dnspython message paths |
+| `celatim[ssh]` | Paramiko SSH message paths |
+| `celatim[iot]` | aiocoap and paho-mqtt message paths |
+| `celatim[realtime]` | WebSocket message paths |
+
+For example:
+
+```bash
+python -m pip install 'celatim[packet,crypto,daemon]'
+```
+
+## Python API
+
+The top-level API covers common endpoint operations and typed results:
+
+```python
+from celatim import PayloadSource, roundtrip_payload
+
+result = roundtrip_payload(
+    "http2-ping-opaque",
+    PayloadSource.hex("00 ff 80 41"),
+)
+assert result.ok
+assert result.payload == b"\x00\xff\x80A"
+```
+
+Mechanism discovery exposes executable transport metadata without importing optional
+stacks:
+
+```python
+from celatim import MechanismProfile
+
+profile = MechanismProfile.from_catalog("http2-ping-opaque")
+print([path.kind.value for path in profile.adapter.paths])
+```
+
+The public API also includes scenario discovery, evidence generation, pcap decode and
+scrub helpers, timing sweeps, installation checks, testbed requirements, and packaged
+document/schema inspection. Lower-level codecs, PDU implementations, detector rules,
+and transport classes remain available through focused `celatim.*` submodules.
+
+## Command line
+
+Inspect mechanisms and packaged contracts:
+
+```bash
+celatim mechanism list
+celatim mechanism show http2-ping-opaque
+celatim scenario list
+celatim docs list
+celatim schema list
+celatim testbed requirements
+```
+
+Run an in-memory binary-payload round trip:
+
+```bash
+celatim roundtrip \
+  --mechanism http2-ping-opaque \
+  --hex "00 ff 80 41"
+```
+
+Run a packaged non-privileged pcap scenario and write evidence:
+
+```bash
+celatim scenario run \
+  --scenario-id http2-ping-opaque-real-pdu-smoke \
+  --artifact-dir out/carriers \
+  --pcap-dir out/pcaps \
+  --log-dir out/logs \
+  --output out/evidence.json
+```
+
+Generate defensive artifacts:
+
+```bash
+celatim detector rules \
+  --output-dir out/detector-rules \
+  --output out/detector-rules.json
+celatim guidance generate --output out/detector-scrub-guidance.md
+celatim guidance windows-capture --output out/windows-capture-guidance.md
+```
+
+## Architecture
+
+Celatim is one PEP 621 project with one `celatim` package:
+
+- `celatim.channel`: bit packing, codecs, framing, and transport-agnostic drivers.
+- `celatim.pdu`: parser-visible protocol data-unit implementations.
+- `celatim.transports`: in-memory, file, pcap, timing, and production-path transports.
+- `celatim.testbed`: netns/veth, AF_PACKET, daemon, tcpdump, and QEMU/TAP helpers.
+- `celatim.detect`: detector predicates, executable replay, and offline scrub support.
+- `celatim.metrics`: separate storage, timing, and subliminal capacity models.
+- `celatim.report`: deterministic tables, figures, matrices, and defensive guidance.
+- `celatim.scenario`: versioned scenario loading and controlled execution.
+
+The wheel includes its default catalog, protocol-rate assumptions, JSON Schemas,
+scenario definitions, and operator documentation. CLI defaults resolve those resources
+with `importlib.resources`, so installed commands do not depend on a source checkout.
+
+Optional integrations are imported only when their transport is selected. The installed
+package smoke verifies that a base import does not load Scapy, cryptography, aioquic,
+dnspython, Paramiko, aiocoap, paho-mqtt, or WebSockets.
+
+## Evidence boundaries
+
+Celatim distinguishes structural capability from executed evidence:
+
+- Storage carriers report field width and both header-relative and on-wire density.
+- Timing/count carriers use a separate rate model.
+- Subliminal cryptographic carriers use separate entropy bounds.
+- Evidence records identify the transport, parser validation, controls, endpoint
+  topology, artifact hashes, and claim status.
+- Public indexes contain hashes and classifications rather than sensitive payloads,
+  transcripts, host paths, or reviewer-only artifacts.
+
+Privileged experiments live under `experiments/`. They require explicit operator action
+and do not run during normal installation, import, or non-privileged CI.
+
+The chosen-nonce ECDSA transcript path is likewise research-only. It creates a fresh
+ephemeral key for each local transcript, uses `cryptography`/OpenSSL for curve operations
+and verification, and must not be used with production or long-lived signing keys.
+
+The companion
+[`rfc-tunnel-survey`](https://github.com/mjbommar/rfc-tunnel-survey) repository vendors
+a manifest-verified snapshot of this project alongside the paper, RFC corpus, generated
+figures, and evidence indexes. This repository is the canonical package and PyPI release
+source.
+
+## Development
+
+Install the locked development environment and run every package gate:
+
+```bash
+make ci
+```
+
+That target runs:
+
+1. `uv sync --locked --all-groups`
+2. `uv lock --check`
+3. `uv run ruff format --check .`
+4. `uv run ruff check .`
+5. `uv run ty check`
+6. `uv run pytest`
+7. `scripts/installed_wheel_smoke.py`
+8. `pip-audit` against every locked development and optional dependency
+
+The type gate covers the package, tests, release scripts, and production experiment
+drivers. There are no directory-wide type-check exclusions; optional-stack boundaries
+use their concrete library modules so they remain statically resolvable.
+GitHub runs the same gate on pushes, pull requests, manual dispatches, and a weekly
+schedule so newly published dependency advisories are detected without waiting for a
+source change.
+
+The installed-wheel smoke builds an sdist, builds the wheel from that sdist, installs it
+without dependencies into a fresh virtual environment, changes to a directory outside
+the checkout, and exercises all five console entry points plus representative public API
+and binary-payload workflows. After proving the base import does not load optional
+stacks, it installs every wheel-declared extra into the isolated environment, imports
+each integration dependency, and records the resolved versions.
+
+Build and validate release distributions with:
+
+```bash
+uv build --out-dir dist
+uvx twine check dist/*
+uvx check-wheel-contents dist/*.whl
+```
+
+## Release workflow
+
+GitHub releases trigger `.github/workflows/release.yml`. The workflow requires a tag
+that exactly matches `v<project.version>`, reruns the full CI and installed-package gate,
+validates wheel metadata and contents, and passes verified artifacts to a separate PyPI
+publishing job.
+
+Only that final job receives `id-token: write`, uses the protected `pypi` environment,
+and exchanges GitHub's OIDC identity for a short-lived PyPI credential. No PyPI token is
+stored in the repository. See [`RELEASING.md`](RELEASING.md) for the trusted-publisher
+identity and release procedure.
+
+Celatim is licensed under the [Apache License 2.0](LICENSE). Release validation requires
+the exact SPDX expression and packaged license file in the wheel.

celatim-0.1.0/README.md

@@ -0,0 +1,229 @@
+# Celatim
+
+Celatim is a typed Python 3.14+ toolkit for reproducible research on covert channels
+and steganographic carriers in IETF protocol fields. It provides channel codecs,
+protocol data-unit implementations, controlled endpoint transports, structural capacity
+models, detector and scrub guidance, scenario execution, and evidence artifacts from one
+distribution and one import namespace.
+
+The project accompanies a survey and measurement paper. Its channel and defensive
+implementations are published together so researchers can reproduce the measurements,
+inspect assumptions, and evaluate both communication and normalization behavior.
+
+Use Celatim only in controlled environments and on systems and networks you are
+authorized to test.
+
+## Requirements
+
+- CPython 3.14 or newer.
+- Linux for AF_PACKET, network-namespace, tcpdump, and QEMU/TAP workflows.
+- No optional protocol stack is imported by the base package.
+
+## Installation
+
+```bash
+python -m pip install celatim
+celatim --help
+```
+
+The wheel installs one primary command, `celatim`, plus four deterministic report
+generators from the same codebase:
+
+- `celatim-paper-figures`
+- `celatim-paper-macros`
+- `celatim-paper-tables`
+- `celatim-support-matrix`
+
+## Install profiles
+
+Optional dependencies are grouped by capability:
+
+| Extra | Capability |
+|---|---|
+| `celatim[packet]` | Scapy packet construction, parsing, and pcap integration |
+| `celatim[crypto]` | ECDSA and RSA-PSS transcript experiments |
+| `celatim[daemon]` | hyper-h2 and aioquic production-stack paths |
+| `celatim[dns]` | dnspython message paths |
+| `celatim[ssh]` | Paramiko SSH message paths |
+| `celatim[iot]` | aiocoap and paho-mqtt message paths |
+| `celatim[realtime]` | WebSocket message paths |
+
+For example:
+
+```bash
+python -m pip install 'celatim[packet,crypto,daemon]'
+```
+
+## Python API
+
+The top-level API covers common endpoint operations and typed results:
+
+```python
+from celatim import PayloadSource, roundtrip_payload
+
+result = roundtrip_payload(
+    "http2-ping-opaque",
+    PayloadSource.hex("00 ff 80 41"),
+)
+assert result.ok
+assert result.payload == b"\x00\xff\x80A"
+```
+
+Mechanism discovery exposes executable transport metadata without importing optional
+stacks:
+
+```python
+from celatim import MechanismProfile
+
+profile = MechanismProfile.from_catalog("http2-ping-opaque")
+print([path.kind.value for path in profile.adapter.paths])
+```
+
+The public API also includes scenario discovery, evidence generation, pcap decode and
+scrub helpers, timing sweeps, installation checks, testbed requirements, and packaged
+document/schema inspection. Lower-level codecs, PDU implementations, detector rules,
+and transport classes remain available through focused `celatim.*` submodules.
+
+## Command line
+
+Inspect mechanisms and packaged contracts:
+
+```bash
+celatim mechanism list
+celatim mechanism show http2-ping-opaque
+celatim scenario list
+celatim docs list
+celatim schema list
+celatim testbed requirements
+```
+
+Run an in-memory binary-payload round trip:
+
+```bash
+celatim roundtrip \
+  --mechanism http2-ping-opaque \
+  --hex "00 ff 80 41"
+```
+
+Run a packaged non-privileged pcap scenario and write evidence:
+
+```bash
+celatim scenario run \
+  --scenario-id http2-ping-opaque-real-pdu-smoke \
+  --artifact-dir out/carriers \
+  --pcap-dir out/pcaps \
+  --log-dir out/logs \
+  --output out/evidence.json
+```
+
+Generate defensive artifacts:
+
+```bash
+celatim detector rules \
+  --output-dir out/detector-rules \
+  --output out/detector-rules.json
+celatim guidance generate --output out/detector-scrub-guidance.md
+celatim guidance windows-capture --output out/windows-capture-guidance.md
+```
+
+## Architecture
+
+Celatim is one PEP 621 project with one `celatim` package:
+
+- `celatim.channel`: bit packing, codecs, framing, and transport-agnostic drivers.
+- `celatim.pdu`: parser-visible protocol data-unit implementations.
+- `celatim.transports`: in-memory, file, pcap, timing, and production-path transports.
+- `celatim.testbed`: netns/veth, AF_PACKET, daemon, tcpdump, and QEMU/TAP helpers.
+- `celatim.detect`: detector predicates, executable replay, and offline scrub support.
+- `celatim.metrics`: separate storage, timing, and subliminal capacity models.
+- `celatim.report`: deterministic tables, figures, matrices, and defensive guidance.
+- `celatim.scenario`: versioned scenario loading and controlled execution.
+
+The wheel includes its default catalog, protocol-rate assumptions, JSON Schemas,
+scenario definitions, and operator documentation. CLI defaults resolve those resources
+with `importlib.resources`, so installed commands do not depend on a source checkout.
+
+Optional integrations are imported only when their transport is selected. The installed
+package smoke verifies that a base import does not load Scapy, cryptography, aioquic,
+dnspython, Paramiko, aiocoap, paho-mqtt, or WebSockets.
+
+## Evidence boundaries
+
+Celatim distinguishes structural capability from executed evidence:
+
+- Storage carriers report field width and both header-relative and on-wire density.
+- Timing/count carriers use a separate rate model.
+- Subliminal cryptographic carriers use separate entropy bounds.
+- Evidence records identify the transport, parser validation, controls, endpoint
+  topology, artifact hashes, and claim status.
+- Public indexes contain hashes and classifications rather than sensitive payloads,
+  transcripts, host paths, or reviewer-only artifacts.
+
+Privileged experiments live under `experiments/`. They require explicit operator action
+and do not run during normal installation, import, or non-privileged CI.
+
+The chosen-nonce ECDSA transcript path is likewise research-only. It creates a fresh
+ephemeral key for each local transcript, uses `cryptography`/OpenSSL for curve operations
+and verification, and must not be used with production or long-lived signing keys.
+
+The companion
+[`rfc-tunnel-survey`](https://github.com/mjbommar/rfc-tunnel-survey) repository vendors
+a manifest-verified snapshot of this project alongside the paper, RFC corpus, generated
+figures, and evidence indexes. This repository is the canonical package and PyPI release
+source.
+
+## Development
+
+Install the locked development environment and run every package gate:
+
+```bash
+make ci
+```
+
+That target runs:
+
+1. `uv sync --locked --all-groups`
+2. `uv lock --check`
+3. `uv run ruff format --check .`
+4. `uv run ruff check .`
+5. `uv run ty check`
+6. `uv run pytest`
+7. `scripts/installed_wheel_smoke.py`
+8. `pip-audit` against every locked development and optional dependency
+
+The type gate covers the package, tests, release scripts, and production experiment
+drivers. There are no directory-wide type-check exclusions; optional-stack boundaries
+use their concrete library modules so they remain statically resolvable.
+GitHub runs the same gate on pushes, pull requests, manual dispatches, and a weekly
+schedule so newly published dependency advisories are detected without waiting for a
+source change.
+
+The installed-wheel smoke builds an sdist, builds the wheel from that sdist, installs it
+without dependencies into a fresh virtual environment, changes to a directory outside
+the checkout, and exercises all five console entry points plus representative public API
+and binary-payload workflows. After proving the base import does not load optional
+stacks, it installs every wheel-declared extra into the isolated environment, imports
+each integration dependency, and records the resolved versions.
+
+Build and validate release distributions with:
+
+```bash
+uv build --out-dir dist
+uvx twine check dist/*
+uvx check-wheel-contents dist/*.whl
+```
+
+## Release workflow
+
+GitHub releases trigger `.github/workflows/release.yml`. The workflow requires a tag
+that exactly matches `v<project.version>`, reruns the full CI and installed-package gate,
+validates wheel metadata and contents, and passes verified artifacts to a separate PyPI
+publishing job.
+
+Only that final job receives `id-token: write`, uses the protected `pypi` environment,
+and exchanges GitHub's OIDC identity for a short-lived PyPI credential. No PyPI token is
+stored in the repository. See [`RELEASING.md`](RELEASING.md) for the trusted-publisher
+identity and release procedure.
+
+Celatim is licensed under the [Apache License 2.0](LICENSE). Release validation requires
+the exact SPDX expression and packaged license file in the wheel.