gpu-seal 0.1.0a0__tar.gz

gpu_seal-0.1.0a0/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.

gpu_seal-0.1.0a0/PKG-INFO

@@ -0,0 +1,400 @@
+Metadata-Version: 2.4
+Name: gpu-seal
+Version: 0.1.0a0
+Summary: Tenant-Observable Security and Isolation Assurance for GPU Clouds
+License-Expression: Apache-2.0
+Keywords: gpu,cloud,security,isolation,attestation,measurement
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Security
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: cryptography>=42
+Requires-Dist: numpy<3,>=1.24
+Requires-Dist: jsonschema>=4
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: ruff<0.17,>=0.16; extra == "dev"
+Requires-Dist: types-jsonschema>=4.24; extra == "dev"
+Provides-Extra: cuda
+Requires-Dist: cupy-cuda12x>=13; extra == "cuda"
+Requires-Dist: nvidia-cuda-nvrtc-cu12; extra == "cuda"
+Requires-Dist: nvidia-cuda-runtime-cu12; extra == "cuda"
+Requires-Dist: nvidia-cuda-nvcc-cu12; extra == "cuda"
+Dynamic: license-file
+
+# GPU-SEAL
+
+*Internal codename: GHOSTMETER*
+
+> Measures the GPU you rented, using only ordinary customer privileges, under
+> a strict canary-only data policy. An assurance and measurement framework —
+> **not** an exploitation toolkit.
+
+[![status](https://img.shields.io/badge/status-pre--alpha%20(Phase%200%E2%80%931)-orange)]()
+[![mutations caught](https://img.shields.io/badge/injected%20violations%20caught-38%2F38-brightgreen)]()
+[![licence](https://img.shields.io/badge/licence-Apache--2.0-blue)]()
+
+Repository: <https://github.com/KubixDesiney/gpu-seal> · Current measured
+status: [`docs/STATUS.md`](docs/STATUS.md)
+
+**GPU-SEAL is a tenant-side, canary-only framework that lets GPU-cloud
+customers independently measure memory sanitisation, hardware consistency,
+and isolation controls without accessing other tenants’ data.**
+
+**Primary audience:** security engineers and GPU-cloud decision-makers.
+**Secondary audience:** academic and independent security reviewers.
+
+New to the project, or looking for a specific role's path through the docs
+(engineer, security reviewer, academic reviewer, operator)? Start at the
+[documentation index](docs/INDEX.md).
+
+---
+
+## The problem
+
+A GPU-cloud tenant pays for a clean chip, a specific model, a specific
+region, and isolation from other tenants — and receives an invoice, not
+evidence. Nothing in that commercial relationship lets the customer check any
+of those claims from where they're actually sitting: inside the rented
+instance, with no special access.
+
+The gap is not hypothetical. NVIDIA's own CUDA documentation states that
+memory returned by `cudaMalloc`, `cuMemAlloc`, `cudaMallocManaged`, and
+`cuMemAllocManaged` **"is not cleared,"** and NVIDIA ships an administrative
+`--clear-memory` tool precisely because clearing isn't the default.
+Confidential Computing scrubs memory at Function Level Reset, not within a
+session. MIG's documentation covers *runtime* isolation in detail and says
+nothing about what happens when an instance is destroyed and handed to the
+next tenant.
+
+Nobody measures any of this in the wild, across providers, from the tenant's
+own seat. That's the gap GPU-SEAL targets: turning "everyone knows GPUs might
+leak" into a reproducible, signed, per-provider dataset — or into evidence
+that they don't.
+
+## What it measures
+
+Thirteen probe families ([`CHARTER.md`](CHARTER.md) §9):
+
+- **Memory residue** — device-global VRAM and shared memory, read before any
+  write of our own
+- **Detection-capability control** — a framework-level allocator canary that
+  proves the probe *can* recover a marker when one exists, independent of
+  what the driver does
+- **Isolation & exposure** — device/namespace visibility, allocation-model
+  classification (dedicated vs. shared vs. time-sliced), MIG temporal
+  isolation
+- **Hardware identity** — a topology fingerprint, reproduced from external
+  published research, checked for consistency with an advertised chip class
+- **Location & attestation** — coarse network-location consistency,
+  confidential-computing attestation and channel binding
+
+Every measurement leaves the probe as a signed, schema-validated JSON
+bundle — never as raw memory.
+
+## What it absolutely does not do
+
+GPU-SEAL will never: exploit a provider, escape a VM or container, access
+the host OS, circumvent authentication or billing, read another tenant's
+files, processes, traffic, or data, recover natural-language text from
+memory it didn't write, classify unknown memory content, retain raw unknown
+VRAM, attempt Rowhammer / privilege escalation / denial of service, or
+publish an uncoordinated accusation.
+
+It searches only for cryptographic canaries it minted itself — there is no
+API that accepts a caller-supplied search pattern, and static analysis
+(`tests/safety/test_static_analysis.py`) rejects source that tries. Full
+policy, with an enforcement point named for every rule: [`ETHICS.md`](ETHICS.md).
+
+---
+
+## Current status
+
+No provider measurement study has been run or validated. The current checkout
+has a green local Python contract and a real local RTX 3050 smoke result, but
+it is not a provider result and is not a release candidate. The policy matrix
+has two complete records and two records awaiting written permission. Ethics
+sign-off, Linux/MIG/H100/same-model validation, and owner decisions remain
+open. See the dated [status snapshot](docs/STATUS.md) for the measured counts
+and exact gate outcomes.
+
+---
+
+## Quickstarts
+
+The commands below separate software verification, simulated runs, and real
+CUDA observations. A simulated result is a test fixture: it is always marked
+`backend_is_real=false` and cannot be published as hardware or provider
+evidence.
+
+### Linux or WSL2
+
+From a Bash shell in a fresh checkout:
+
+```bash
+git clone https://github.com/KubixDesiney/gpu-seal.git
+cd gpu-seal
+python3 -m venv .venv
+. .venv/bin/activate
+python -m pip install --no-build-isolation -e ".[dev]"
+python -m pytest tests -q
+python lab/check-provider-policy.py
+python lab/local-runner/smoke.py
+```
+
+Validation note for this snapshot: the PowerShell quickstart and Git Bash
+negative control were run on Windows. WSL2 was unavailable in the managed
+session (`E_ACCESSDENIED`), so Linux/WSL2 hardware evidence still needs a
+supported Linux or WSL2 host run.
+
+For the safety negative control, use a working Bash installation:
+
+```bash
+PYTHON_BIN="$(command -v python)" bash lab/verify-safety-suite.sh
+```
+
+Real CUDA work in WSL2 additionally requires the Windows NVIDIA driver, WSL2
+GPU integration, Docker Desktop WSL integration if using containers, and the
+NVIDIA Container Toolkit. Do not install a Linux NVIDIA driver inside WSL2.
+The full container setup is in [`lab/docker/README.md`](lab/docker/README.md).
+
+### Windows PowerShell
+
+From the repository root, use Python 3.10 or newer in an isolated environment:
+
+```powershell
+python -m venv .venv
+.\.venv\Scripts\Activate.ps1
+python -m pip install --no-build-isolation -e ".[dev]"
+python -m pytest tests -q
+python lab/check-provider-policy.py
+python lab/local-runner/smoke.py
+```
+
+The safety battery needs Bash. Run it from WSL2 or Git Bash with the Python
+interpreter selected for that shell. PowerShell itself is sufficient for the
+unit/safety suite, the policy check, simulated runs, and the local smoke check.
+
+For a real CUDA backend on bare metal, install the CUDA extra as well:
+
+```powershell
+python -m pip install --no-build-isolation -e ".[dev,cuda]"
+```
+
+The `cuda` extra provides CuPy and the Python CUDA runtime/compiler components
+used by the probes. Native compilation still requires a compatible CUDA
+toolkit/compiler or the pinned CUDA container; the extra does not establish
+native conformance.
+
+### First successful verification
+
+1. Run `python -m pytest tests -q`; the checkout measured 430 passed as of the
+   2026-09-11 run recorded in [`docs/STATUS.md`](docs/STATUS.md).
+2. Run `python lab/check-provider-policy.py`; expect 2 complete, 2 awaiting,
+   and `GATE: lifted`. This does not authorize all providers.
+3. Run `python lab/local-runner/run_phase1.py --simulate --size-mib 1
+   --cycles 2 --unsafe-development-ephemeral --out ./out-simulated`; expect
+   exit 0 and a non-publishable result with `backend_is_real=false`. For any
+   provenance-suitable bundle, replace the explicit development flag with
+   `--signing-key <caller-supplied-ed25519.pem>`.
+4. Run `python lab/local-runner/smoke.py`. Only a `CupyBackend` report with
+   `backend_is_real=true` is a real local CUDA observation; it is still not
+   provider validation.
+
+To verify a signed bundle, obtain the expected public key through an
+independent trusted channel and use the CLI with that external key:
+
+```bash
+gpu-seal verify ./out/<run-id>.result.json --public-key ./trusted-ed25519.pem
+```
+
+See [`docs/TRUST-MODEL.md`](docs/TRUST-MODEL.md) for the distinction between
+dashboard inspection and cryptographic verification. A non-pinned local run
+does not satisfy the publication provenance gate; use the pinned CUDA image
+for evidence intended for publication.
+
+The repository-owned campaign harness is also available without a provider:
+
+```bash
+python -m gpu_seal campaign run \
+  --ownership-confirmation "local deterministic validation" \
+  --confirmed-by researcher \
+  --unsafe-development-ephemeral
+```
+
+This command uses only the deterministic fake runtime. It exercises campaign
+sequencing, timeouts, cleanup reconciliation, and signed storage; it does not
+contact a provider or produce hardware evidence. The provider adapter boundary
+and its owner inputs are documented in [`docs/PROVIDER-ADAPTER.md`](docs/PROVIDER-ADAPTER.md).
+
+---
+
+## Example output (trimmed)
+
+```json
+{
+  "provider_code": "local-lab",
+  "product_claim": "NVIDIA GeForce RTX 3050 Laptop GPU",
+  "probes": [
+    {
+      "probe_name": "framework_allocator_reuse",
+      "measurement_path": "framework_pooled",
+      "zero_fraction": 0.9999748,
+      "owned_canary_match": true,
+      "owned_canary_exact_matches": 8
+    },
+    {
+      "probe_name": "memory_global_read_before_write",
+      "measurement_path": "driver_direct",
+      "zero_fraction": 1.0,
+      "owned_canary_match": false,
+      "owned_canary_exact_matches": 0
+    }
+  ],
+  "report_card": {
+    "note": "Independent category grades, no composite score. U means unproven, not failing.",
+    "memory_lifecycle_hygiene": {
+      "grade": "U",
+      "basis": "No canaries recovered, but same-model die separation (§9.8b) is not yet validated — a clean result cannot distinguish sanitisation from a different physical chip."
+    },
+    "hardware_claim_consistency": {
+      "grade": "A",
+      "basis": "Topology certificate strongly consistent with the advertised class."
+    },
+    "allocation_model_transparency": {
+      "grade": "C",
+      "basis": "Undocumented by the provider; inferred as time_sliced_full_gpu at confidence 0.80."
+    }
+  },
+  "safety": {
+    "raw_unknown_memory_retained": false,
+    "unknown_memory_rendered": false,
+    "canary_only_search": true
+  }
+}
+```
+
+`memory_lifecycle_hygiene` grading **U** next to `hardware_claim_consistency`
+grading **A**, in the same bundle, is intentional: grades are independent per
+category, and **U means the evidence doesn't support a claim yet — not that
+anything failed.** Real, untrimmed bundle:
+[`examples/sample-safe-result.json`](examples/sample-safe-result.json).
+
+---
+
+## Architecture
+
+```
+ rented GPU instance
+        │
+        ▼
+┌────────────────────────────┐
+│ Controller                 │  provider allowlist · ownership attestation
+│ gpu_seal.controller        │  duration ceiling · budget · disclosure gate
+└──────────────┬─────────────┘
+               │ deploys
+               ▼
+┌────────────────────────────┐
+│ Probe agent                │  13 families, §9.1–§9.12
+│ gpu_seal.probes            │
+└──────────────┬─────────────┘
+               │ all unknown memory passes through here
+               ▼
+┌────────────────────────────┐
+│ Enforced-safe layer        │  SafeBuffer: fill_via() is the only write
+│ gpu_seal.safety            │  door, aggregate() the only read door
+└──────────────┬─────────────┘
+               │ allowlisted statistics only
+               ▼
+┌────────────────────────────┐
+│ Signed evidence bundle     │  Ed25519 + SHA-256, schema-validated,
+│ gpu_seal.evidence          │  report card, no composite score
+└────────────────────────────┘
+```
+
+Full component map and the reasoning behind each boundary:
+[`docs/architecture.md`](docs/architecture.md).
+
+---
+
+## Roadmap — CHARTER.md §17
+
+- [x] Wk 1–2 Foundation — threat model, ethics/disclosure policy, schemas,
+      prior-art sweep
+- [x] Wk 3–4 Local probe core — built, run on real silicon, §9.4 control
+      validated
+- [x] Wk 5–6 Exposure & container tests — §9.1 / §9.6 running, NVML wired in
+- [x] Wk 7–8 Topology + allocation classifier — §9.8 reproduced on silicon,
+      §9.7 classifier built
+- [ ] Wk 9–10 Provider pilot — blocked on ethics approval, provider
+      permissions, pinned native conformance, and owner launch decisions
+- [~] Wk 11 Attestation module — built and tested; needs H100-class CC
+      hardware to exercise
+- [~] Wk 12 Release + preprint — tooling and docs are present; public release
+      remains blocked by the dirty-tree gate and unresolved human/external
+      validation decisions
+
+**Next concrete steps:** review the current dirty tree, obtain the two
+outstanding written permissions, get ethics sign-off, and schedule the pinned
+native/Linux and same-model validation work. Do not start provider testing from
+this quickstart.
+
+---
+
+## Standing on prior work
+
+GPU-SEAL reuses, rather than reinvents,
+[Alpay & Alpay (2026), *Unprivileged Topology Certificates for Cloud GPU
+Attestation*](https://arxiv.org/abs/2606.24934) for hardware-class and
+coarse-location attestation. Their instrument answers *which chip did I get,
+and roughly where is it?* GPU-SEAL asks the question they leave open: *what
+was left on it, and does the provider's isolation model match what they sold
+you?* Their paper explicitly leaves same-model die separation unresolved
+(§12); the report card refuses grade A on memory hygiene until that's
+closed, and CI enforces the refusal. Details: [`docs/prior-art.md`](docs/prior-art.md).
+
+---
+
+## Documentation
+
+Role-based navigation (start here, run locally, safety model, methodology,
+provider testing, release checklist): [`docs/INDEX.md`](docs/INDEX.md).
+
+Full flat list, by content:
+
+| Document | Contents |
+|---|---|
+| [`docs/PROGRESS.md`](docs/PROGRESS.md) | Implementation progress, category assessment, and boundaries |
+| [`docs/REMAINING.md`](docs/REMAINING.md) | What is left, ordered by what actually unblocks the project |
+| [`docs/STATUS.md`](docs/STATUS.md) | Dated measured release-readiness snapshot |
+| [`docs/OWNER-ACTION-CHECKLIST.md`](docs/OWNER-ACTION-CHECKLIST.md) | Human decisions and external inputs |
+| [`docs/TRUST-MODEL.md`](docs/TRUST-MODEL.md) | Dashboard inspection and cryptographic verification |
+| [`docs/RELEASE.md`](docs/RELEASE.md) | Release process and automated-gate limits |
+| [`docs/TROUBLESHOOTING.md`](docs/TROUBLESHOOTING.md) | Setup, platform, and evidence FAQ |
+| [`CHARTER.md`](CHARTER.md) | Governing research and implementation charter |
+| [`ETHICS.md`](ETHICS.md) | Ethics policy, with the enforcement point named for every rule |
+| [`docs/threat-model.md`](docs/threat-model.md) | Tenant position, adversary model, hard boundaries |
+| [`docs/methodology.md`](docs/methodology.md) | How a measurement is taken, and what it may conclude |
+| [`docs/scoring.md`](docs/scoring.md) | The report card, and why there is no composite score |
+| [`docs/pre-registration.md`](docs/pre-registration.md) | Hypotheses and thresholds, fixed before any provider data |
+| [`docs/architecture.md`](docs/architecture.md) | Full component map and design principles |
+| [`docs/data-handling.md`](docs/data-handling.md) | What is held, for how long, and what is refused outright |
+| [`DISCLOSURE.md`](DISCLOSURE.md) | Responsible disclosure process |
+| [`docs/provider-policy-review/`](docs/provider-policy-review/) | The Phase 0 gate: no reviewed record, no probing |
+| [`docs/adr/`](docs/adr/) | Architecture decision records |
+| [`SECURITY.md`](SECURITY.md) | Reporting vulnerabilities in GPU-SEAL itself |
+| [`CONTRIBUTING.md`](CONTRIBUTING.md) | Contribution workflow and required checks |
+| [`CODE_OF_CONDUCT.md`](CODE_OF_CONDUCT.md) | Participation standards |
+| [`CHANGELOG.md`](CHANGELOG.md) | Release notes and change policy |
+
+---
+
+## Licence & citation
+
+Apache-2.0 — see [`LICENSE`](LICENSE). Citation metadata is in
+[`CITATION.cff`](CITATION.cff).