ciris-server 0.2.6__tar.gz → 0.3.0__tar.gz

{ciris_server-0.2.6 → ciris_server-0.3.0}/.github/workflows/bench.yml

@@ -52,7 +52,7 @@ jobs:
         with:
           python-version: "3.12"
       - name: Run benches (criterion)
-        run: cargo bench --bench pqc_av_streaming --bench replication_ingest --bench alm_chain
+        run: cargo bench --bench pqc_av_streaming --bench replication_ingest --bench alm_chain --bench stream_fanout
       - name: Generate holonomic scoreboard (CIRISServer#12/#13)
         run: cargo run --release --quiet -- scoreboard > scoreboard.json
       - name: Generate interpreted page

{ciris_server-0.2.6 → ciris_server-0.3.0}/.github/workflows/ci.yml

@@ -46,6 +46,16 @@ jobs:
       # `extension-module` (libpython-no-link) into the test binary.
       - run: cargo clippy --all-targets -- -D warnings
       - run: cargo test
+      # The NOISE FLOOR proof (CIRISServer#14, CEG §19.7 / §19.3 N5) — provable
+      # individual-unrecoverability for erasure compliance, run explicitly so the
+      # MEASURED residual-fidelity numbers land in the CI log (Linux only — one
+      # canonical record; the test also runs on every OS via `cargo test` above).
+      # The three gated cases: (a) revocation ⇒ EjectHardDelete leaves NO
+      # recoverable tier, (b) the measured noise floor below n_source symbols,
+      # (c) N→1 aggregation erases the individual below the 1/N gist bound.
+      - name: Noise floor proof (MEASURED, Linux)
+        if: runner.os == 'Linux'
+        run: cargo test --test noise_floor -- --nocapture
       # The PyO3 wheel surface (Linux only; libpython linked, no extension-module).
       - name: clippy (python surface, Linux)
         if: runner.os == 'Linux'

{ciris_server-0.2.6 → ciris_server-0.3.0}/.github/workflows/publish-pypi.yml

@@ -243,3 +243,7 @@ jobs:
           packages-dir: dist/
           # Trusted Publishing: no `password:` — the OIDC identity is verified
           # against the publisher registered on PyPI.
+          # Idempotent re-cuts: if a tag is re-cut onto a new commit, the wheels
+          # for any platform already on PyPI are skipped instead of 400-ing the
+          # whole upload — a clean re-cut publishes only the newly-built files.
+          skip-existing: true

{ciris_server-0.2.6 → ciris_server-0.3.0}/.github/workflows/release.yml

@@ -38,19 +38,26 @@ jobs:
   build-native:
     name: Build (${{ matrix.target }})
     runs-on: ${{ matrix.os }}
+    # Allowed-to-fail lanes (the TPM backend can't cross-compile) never block the
+    # release; see the armv7 entry + the build-musl job.
+    continue-on-error: ${{ matrix.allow_fail || false }}
     strategy:
       fail-fast: false
       matrix:
         include:
           - os: ubuntu-latest
             target: x86_64-unknown-linux-gnu
-          - os: ubuntu-latest
+          # ARM64 builds NATIVELY on an ARM runner (apt libtss2-dev applies) —
+          # cross-compiling tss-esapi from x86 has no target libtss2.
+          - os: ubuntu-24.04-arm
             target: aarch64-unknown-linux-gnu
-            cross: true
-          # ARM32 — Raspberry Pi / embedded mesh nodes.
+          # ARM32 — Raspberry Pi / embedded mesh nodes. Cross-builds the TPM
+          # backend with no target libtss2 → allowed-to-fail (CIRISServer#7);
+          # never blocks the release.
           - os: ubuntu-latest
             target: armv7-unknown-linux-gnueabihf
             cross: true
+            allow_fail: true
           - os: macos-latest
             target: x86_64-apple-darwin
           - os: macos-latest
@@ -134,6 +141,9 @@ jobs:
   build-musl:
     name: Build (aarch64 musl)
     runs-on: ubuntu-latest
+    # zigbuild cross can't satisfy the TPM backend's target libtss2 — allowed to
+    # fail so it never blocks the release (aarch64-gnu native covers ARM64 Linux).
+    continue-on-error: true
     steps:
       - uses: actions/checkout@v4
       - uses: dtolnay/rust-toolchain@stable
@@ -170,6 +180,10 @@ jobs:
   create-release:
     name: Create Release
     needs: [build-native, build-musl]
+    # Run as long as the build stage finished (not cancelled) — the allowed-to-fail
+    # ARM lanes (armv7 cross, aarch64 musl) must not skip the release; it ships
+    # whatever built (x86_64 linux/mac/win + aarch64-linux-gnu native).
+    if: ${{ !cancelled() }}
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4

{ciris_server-0.2.6 → ciris_server-0.3.0}/CHANGELOG.md

@@ -4,6 +4,67 @@ All notable changes to CIRISServer. Format follows [Keep a Changelog](https://ke
 this project uses [Semantic Versioning](https://semver.org/). The minor line tracks
 the fabric-node scope (0.1 lens · 0.5 +registry · 1.0 +node), paced by the CIRISAgent train.
 
+## [0.3.0] — 2026-06-16
+
+The integrated fabric node: the **auth subsystem** absorbed, the **one-wheel**
+re-export surface, and the substrate on the **v8.4.0 / v4.3.0 / v5.10.0** floor.
+This is the node we replace the deployed CIRISLens with (and the wheel CIRISAgent
+adopts to drop its lens-core + its own auth).
+
+### Added
+- **Auth subsystem (`src/auth/`, CIRISServer#9) — the fabric is the single auth
+  authority.** The agent's entire user/WA/OAuth/api-key/service-token surface
+  already lived in one persist table (`wa_cert`), so this is a Python→Rust port
+  over the same rows — **no schema fork, 0 conflicts** (`src/auth/ABSORPTION.md`:
+  33 capabilities mapped). One `x-ciris-*` hybrid request verifier (accepts the
+  identity **or** any admitted occurrence — the consenting user *and* the
+  generating agent are both valid signers); **self-at-login** (§8.1.12.7) as the
+  login ceremony; OAuth front-door (providers/login/callback + native
+  google/apple); sessions/token issuer (replaces OAuth→WA→JWT); the CEG role-set
+  **plus** the agent's `UserRole`/`Permission` model verbatim; api-keys +
+  service-token revocation; attestation; user-signed **consent**; and CEG-native
+  **erasure** (GDPR Art. 17 in-app path → `Engine::evict_actor`). Password KDF,
+  native-token JWKS, and root-signature verification are byte-compatible with the
+  agent's own crypto (verified against agent-produced vectors).
+- **One-wheel re-export (CIRISServer#4):** `ciris_server` re-hosts the persist /
+  edge / lens Python surfaces under one `.so` (one PyO3 type registry —
+  `ciris_server.Engine is ciris_server.persist.Engine`), so CIRISAgent consumes a
+  single wheel and the cross-wheel type-identity bug class (CIRISPersist#109)
+  cannot occur. (`reset_engine` / `init_edge_runtime` re-export hooks pending
+  upstream: CIRISPersist#231, CIRISEdge#156; `ciris-verify` stays a standalone
+  ctypes wheel.)
+- **Noise-floor compliance bench (CIRISServer#14, `tests/noise_floor.rs`):**
+  measured individual-unrecoverability — revocation → hard-delete, the
+  reconstruction cliff at the fountain floor, aggregation-is-erasure.
+- **The fabric app (`app/`, CIRISServer#15):** the CIRISAgent KMP mesh app minus
+  agent cards (identity slice proven; governance/safety surfaces).
+
+### Changed
+- Substrate floor → **persist v8.4.0 / edge v4.3.0 / verify-family v5.10.0** (the
+  §19.7 erasure primitives + `wa_cert` auth substrate).
+
+### Validated
+- **Behavior-correct drop-in proof (`qa/`, `FSD/QA_AGAINST_RUST.md`).** The agent's
+  own Python QA-runner module definitions are run unmodified against a live Rust
+  `ciris-server`: **12/12 fabric-route tests pass, 0 gaps** — including the
+  load-bearing byte-compat proof that a password hash produced by the agent's own
+  `cryptography.PBKDF2HMAC` authenticates against the Rust `verify_password`. The
+  ~30 agent-brain modules are correctly N/A on a headless fabric node. The QA
+  runner stays Python (it is HTTP-driving conformance, not ported).
+
+### Fixed
+- **api-keys / service-token routes are now authz-gated.** `POST/GET/DELETE
+  /v1/auth/api-keys*` and `/v1/auth/service-token/revoke` now require a live
+  session bearer whose role carries `manage_user_permissions` (matching the
+  agent's gate) — the one residual the conformance run surfaced.
+
+### Notes
+- Companion: **CIRISStatus** becomes a fabric monitoring node (Flows A/B +
+  `health:liveness` `scores` + website sockets).
+- GDPR erasure is **both** entry points: the DSAR endpoint on the monitor node
+  **and** the in-app CEG-native `withdraws`. Full lens decommission stays gated on
+  the DSAR-via-status endpoint landing (keep the Python DSAR reachable until then).
+
 ## [0.2.6] — 2026-06-16
 
 Substrate floor → **v4.2.0 family** + the **multi-tier ALM relay chain** test

{ciris_server-0.2.6 → ciris_server-0.3.0}/Cargo.lock

@@ -812,8 +812,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-crypto"
-version = "5.9.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.9.0#27fc6dab0fd2efa58bea8648bc241c3852d9435f"
+version = "5.10.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.10.0#be2511433a2ef14d315571655933ecf9d05699e1"
 dependencies = [
  "ed25519-dalek",
  "hex",
@@ -838,8 +838,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-edge"
-version = "4.2.0"
-source = "git+https://github.com/CIRISAI/CIRISEdge?tag=v4.2.0#08d9e05a672d2978dd65230d398d78e0a6f7586b"
+version = "4.3.0"
+source = "git+https://github.com/CIRISAI/CIRISEdge?tag=v4.3.0#ab4f1bc49783faa470472ea577a3f4cf10b37e28"
 dependencies = [
  "async-trait",
  "axum",
@@ -863,6 +863,7 @@ dependencies = [
  "pyo3",
  "pyo3-async-runtimes",
  "qrcodegen",
+ "raptorq",
  "rcgen",
  "reqwest",
  "reticulum-core",
@@ -889,8 +890,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-keyring"
-version = "5.9.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.9.0#27fc6dab0fd2efa58bea8648bc241c3852d9435f"
+version = "5.10.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.10.0#be2511433a2ef14d315571655933ecf9d05699e1"
 dependencies = [
  "aes-gcm",
  "async-trait",
@@ -953,8 +954,8 @@ dependencies = [
 
 [[package]]
 name = "ciris-persist"
-version = "8.2.0"
-source = "git+https://github.com/CIRISAI/CIRISPersist?tag=v8.2.0#0d12e232339f604a77e8ffc030eef0bccd7d5e8e"
+version = "8.4.0"
+source = "git+https://github.com/CIRISAI/CIRISPersist?tag=v8.4.0#7b40aae71cc17683f5cfb9553f1d484d267f1970"
 dependencies = [
  "async-trait",
  "base64 0.22.1",
@@ -993,9 +994,10 @@ dependencies = [
 
 [[package]]
 name = "ciris-server"
-version = "0.2.6"
+version = "0.3.0"
 dependencies = [
  "anyhow",
+ "async-trait",
  "axum",
  "base64 0.22.1",
  "chrono",
@@ -1010,19 +1012,27 @@ dependencies = [
  "flate2",
  "fs2",
  "getrandom 0.3.4",
+ "hex",
+ "hmac 0.12.1",
+ "jsonwebtoken",
+ "pbkdf2",
  "pyo3",
  "pyo3-async-runtimes",
+ "reqwest",
  "serde",
  "serde_json",
+ "sha2 0.10.9",
+ "subtle",
  "tokio",
  "tracing",
  "tracing-subscriber",
+ "urlencoding",
 ]
 
 [[package]]
 name = "ciris-verify-core"
-version = "5.9.0"
-source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.9.0#27fc6dab0fd2efa58bea8648bc241c3852d9435f"
+version = "5.10.0"
+source = "git+https://github.com/CIRISAI/CIRISVerify?tag=v5.10.0#be2511433a2ef14d315571655933ecf9d05699e1"
 dependencies = [
  "android_system_properties",
  "anyhow",
@@ -1242,7 +1252,7 @@ dependencies = [
  "criterion-plot",
  "futures",
  "is-terminal",
- "itertools 0.10.5",
+ "itertools",
  "num-traits",
  "once_cell",
  "oorandom",
@@ -1264,7 +1274,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "6b50826342786a51a89e2da3a28f1c32b06e387201bc2d19791f622c673706b1"
 dependencies = [
  "cast",
- "itertools 0.10.5",
+ "itertools",
 ]
 
 [[package]]
@@ -2828,15 +2838,6 @@ dependencies = [
  "either",
 ]
 
-[[package]]
-name = "itertools"
-version = "0.12.1"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "ba291022dbbd398a455acf126c1e341954079855bc60dfdda641363bd6922569"
-dependencies = [
- "either",
-]
-
 [[package]]
 name = "itoa"
 version = "1.0.18"
@@ -2933,9 +2934,11 @@ checksum = "5a87cc7a48537badeae96744432de36f4be2b4a34a05a5ef32e9dd8a1c169dde"
 dependencies = [
  "base64 0.22.1",
  "js-sys",
+ "pem",
  "ring",
  "serde",
  "serde_json",
+ "simple_asn1",
 ]
 
 [[package]]
@@ -4392,7 +4395,7 @@ checksum = "22505a5c94da8e3b7c2996394d1c933236c4d743e81a410bcca4e6989fc066a4"
 dependencies = [
  "bytes",
  "heck",
- "itertools 0.12.1",
+ "itertools",
  "log",
  "multimap",
  "once_cell",
@@ -4412,7 +4415,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "81bddcdb20abf9501610992b6759a4c888aef7d1a7247ef75e2404275ac24af1"
 dependencies = [
  "anyhow",
- "itertools 0.12.1",
+ "itertools",
  "proc-macro2",
  "quote",
  "syn 2.0.117",
@@ -4681,6 +4684,12 @@ dependencies = [
  "rand_core 0.9.5",
 ]
 
+[[package]]
+name = "raptorq"
+version = "2.0.1"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "4d4215fb79ef19442a0c71616aabb0715a386e6a16ed9031775ee3e3f20e7502"
+
 [[package]]
 name = "rayon"
 version = "1.12.0"
@@ -5583,6 +5592,18 @@ version = "0.3.9"
 source = "registry+https://github.com/rust-lang/crates.io-index"
 checksum = "703d5c7ef118737c72f1af64ad2f6f8c5e1921f818cdcb97b8fe6fc69bf66214"
 
+[[package]]
+name = "simple_asn1"
+version = "0.6.4"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "0d585997b0ac10be3c5ee635f1bab02d512760d14b7c468801ac8a01d9ae5f1d"
+dependencies = [
+ "num-bigint",
+ "num-traits",
+ "thiserror 2.0.18",
+ "time",
+]
+
 [[package]]
 name = "siphasher"
 version = "1.0.3"

{ciris_server-0.2.6 → ciris_server-0.3.0}/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ciris-server"
-version = "0.2.6"   # 0.1 = lens-only (agent ~2.9.7); 0.5 = +registry (~2.9.8); 1.0 = +node (~2.9.10). Patch forward (0.1.1) on breakage.
+version = "0.3.0"   # 0.1 = lens-only (agent ~2.9.7); 0.3 = +auth subsystem / one-wheel; 0.5 = +registry (~2.9.8); 1.0 = +node (~2.9.10). Patch forward on breakage.
 edition = "2021"
 # MSRV floor is set by the substrate: ciris-verify v5.2.0 requires 1.86
 # (persist v6.0.1 is 1.83). Build with the higher of the two.
@@ -37,10 +37,32 @@ path = "src/main.rs"
 default = []
 # `python` pulls the PyO3 bindings (for the wheel). The binary builds WITHOUT it,
 # so a plain `cargo build` never links libpython.
-python = ["dep:pyo3", "dep:pyo3-async-runtimes", "ciris-lens-core/python"]
+# ONE-WHEEL RE-EXPORT (CIRISServer#4): `python` ALSO turns on the substrate
+# crates' OWN pyo3 surfaces (`ciris-persist/pyo3`, `ciris-edge/pyo3`) so their
+# `#[pyclass]`es compile into THIS cdylib — one `.so`, one PyO3 type registry,
+# so the persist `Engine` handed to edge is the SAME type both sides see (the
+# CIRISPersist#109 cross-wheel type-identity bug CANNOT occur). persist names its
+# feature `pyo3` (not `python`); edge likewise, and edge's `pyo3` already pulls
+# `ciris-persist/pyo3` transitively — both listed for explicitness. verify is
+# deliberately ABSENT: it is a ctypes wheel (libciris_verify_ffi.so via
+# ctypes.CDLL), not a `#[pymodule]`, so it cannot be a pyo3 submodule.
+python = [
+    "dep:pyo3",
+    "dep:pyo3-async-runtimes",
+    "ciris-lens-core/python",
+    "ciris-persist/pyo3",
+    "ciris-edge/pyo3",
+]
 # `extension-module` is what maturin builds the wheel with (tells PyO3 not to
 # link libpython). The bin must NOT enable it. See pyproject.toml [tool.maturin].
-extension-module = ["python", "pyo3/extension-module"]
+# Propagated to the substrate crates so THEIR pyo3 surfaces also skip linking
+# libpython (each crate gates `extension-module` as its own feature).
+extension-module = [
+    "python",
+    "pyo3/extension-module",
+    "ciris-persist/extension-module",
+    "ciris-edge/extension-module",
+]
 # NOTE: hardware key custody (TPM/SE/StrongBox) is wired per-TARGET below, not as
 # a cargo feature — TPM (tss-esapi) is Linux-only, so a top-level `tpm` feature
 # made `--all-features` drag tss-esapi onto Windows/macOS (where it can't build).
@@ -54,7 +76,7 @@ extension-module = ["python", "pyo3/extension-module"]
 # libraries over ONE shared persist Engine (registry + lens read/write the same
 # corpus in-process; per-slice views via Engine::from_shared).
 #
-# Substrate floor (SHIPPED): persist v8.2.0 / edge v4.2.0 / verify-family v5.9.0
+# Substrate floor (SHIPPED): persist v8.4.0 / edge v4.3.0 / verify-family v5.10.0
 # (ciris-keyring + ciris-crypto + ciris-verify-core), CEG 1.0-RC12. The composition
 # root pins the singleton construction; the in-tree ciris-lens-core co-bumps in
 # lockstep (MAJOR caret pins persist "8" / edge "4"). edge v4.2.0 ships the relay
@@ -76,16 +98,19 @@ ciris-lens-core     = { path = "crates/ciris-lens-core" } # ABSORBED in-tree (wo
 # sqlite on all platforms; postgres is Linux-only (libpq/openssl don't link
 # cleanly on the macOS/Windows runners — same posture as persist's own CI). The
 # `[target.linux]` table below adds postgres.
-ciris-persist     = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.2.0", features = ["sqlite"] }
-ciris-edge        = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.2.0", features = ["transport-reticulum", "transport-http"] }
+# `cirislens_wa_cert` + `cirislens_service_token_revocation` expose the auth
+# substrate the fabric absorbs (CIRISServer#9, src/auth): the agent's `wa_cert`
+# table (users/WA/OAuth/api-keys) + the `revoked_service_tokens` table.
+ciris-persist     = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.4.0", features = ["sqlite", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
+ciris-edge        = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.3.0", features = ["transport-reticulum", "transport-http"] }
 # Founder-quorum verification + key-id fingerprint at the composition root
 # (threshold:: module path — NOT re-exported at the crate root).
-ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.9.0" }
+ciris-verify-core = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.10.0" }
 # Hardware-backed transport-identity keystore (verify v5.2.0 #68 / edge #99).
 # Base = software keystore + byte-identical migration of an existing .rid (works
 # everywhere, no libtss2). The real TPM-2.0 / SE / StrongBox backend rides the
 # `tpm` feature; runtime auto-detects hardware and falls back to software.
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.9.0", version = "5", features = ["software", "pqc-ml-dsa"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.10.0", version = "5", features = ["software", "pqc-ml-dsa"] }
 
 # PyO3 bindings for the abi3 wheel — optional, gated behind the `python` feature
 # so the binary never links them. 0.29 matches the persist/edge family floor.
@@ -102,6 +127,31 @@ base64     = "0.22"
 serde      = { version = "1", features = ["derive"] } # holonomic scoreboard model (benchmarks::)
 serde_json = "1"
 getrandom  = "0.3"   # mint the ML-DSA-65 federation seed on first boot (hybrid PQC)
+# Auth subsystem (src/auth, CIRISServer#9): timestamps on the absorbed wa_cert
+# rows, SHA-256 for api-key / service-token hashing, hex for the digest wire form.
+# All three already in the lock as substrate-transitive deps (no new resolution).
+chrono     = { version = "0.4", features = ["serde"] }
+sha2       = "0.10"
+hex        = "0.4"
+# Auth gap-close (CIRISServer#9, src/auth): the byte-compatible password KDF +
+# the OAuth/native/device-auth outbound-HTTP + JWKS-verify halves. All already in
+# the lock as substrate-transitive deps (reqwest/jsonwebtoken via edge+verify;
+# pbkdf2/hmac/ed25519-dalek via the crypto family) — pinned here so the auth
+# subsystem owns them directly, no new resolution.
+# - pbkdf2 + hmac: reproduce the agent's PBKDF2-HMAC-SHA256(100k) password hash
+#   (auth_service.py `_hash_password`/`_verify_password`) byte-for-byte.
+# - ed25519-dalek: verify the ROOT mint signature (the agent's `verify_root_signature`).
+# - jsonwebtoken: Apple Sign-In RS256 JWKS verification.
+# - reqwest (rustls): Google tokeninfo / OAuth code→token / Apple JWKS / Portal HTTP.
+# - urlencoding: build the provider authorize-URL query string (matches urlencode).
+pbkdf2     = { version = "0.12", default-features = false }
+hmac       = "0.12"
+subtle     = "2"     # constant-time password-hash compare (the agent's hmac.compare_digest)
+ed25519-dalek = "2"
+jsonwebtoken  = "9"
+urlencoding   = "2"
+async-trait   = "0.1"  # the ProviderClient HTTP seam (async fn in trait)
+reqwest    = { version = "0.12", default-features = false, features = ["rustls-tls", "json"] }
 flate2     = "1"     # read the gz'd legacy-trace dump (import-traces subcommand)
 tracing = "0.1"
 tracing-subscriber = { version = "0.3", features = ["env-filter", "json"] }
@@ -112,13 +162,13 @@ tracing-subscriber = { version = "0.3", features = ["env-filter", "json"] }
 # - keyring `tpm` (tss-esapi / TPM 2.0) — the real hardware backend; needs
 #   libtss2 (Linux build dep). Other targets keep the software keystore.
 [target.'cfg(target_os = "linux")'.dependencies]
-ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.2.0", features = ["postgres"] }
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.9.0", version = "5", features = ["tpm"] }
+ciris-persist = { git = "https://github.com/CIRISAI/CIRISPersist", tag = "v8.4.0", features = ["postgres", "cirislens_wa_cert", "cirislens_service_token_revocation"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.10.0", version = "5", features = ["tpm"] }
 
 # Android (arm64/arm32/x86_64): the keyring `android` backend (JNI → Android
 # Keystore/StrongBox); sqlite bundles, no postgres/tpm. Mirrors persist/edge.
 [target.'cfg(target_os = "android")'.dependencies]
-ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.9.0", version = "5", features = ["android"] }
+ciris-keyring = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.10.0", version = "5", features = ["android"] }
 
 # Test-only — the two-node replication integration test (tests/replication.rs)
 # builds + signs CEG batches with the same primitives persist verifies against.
@@ -133,7 +183,14 @@ criterion     = { version = "0.5", features = ["async_tokio"] }
 # The PQC primitives the realtime-A/V E2E bench drives directly: hybrid KEX
 # (X25519 + ML-KEM-768) for the per-Link transit key, AES-256-GCM for the
 # two-layer chunk seal. Same pin/features edge composes (tag parity).
-ciris-crypto  = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.9.0", version = "5", features = ["hybrid-kex", "aes-gcm", "pqc-ml-dsa"] }
+ciris-crypto  = { git = "https://github.com/CIRISAI/CIRISVerify", tag = "v5.10.0", version = "5", features = ["hybrid-kex", "aes-gcm", "pqc-ml-dsa"] }
+# Enable edge's OWN fountain codec (`codec-fountain`, L1-A) for the survival-floor
+# proof — dev/test ONLY (feature unification applies to test/bench builds; the
+# shipped wheel stays codec-free, since a relay forwards sealed symbols opaquely
+# and never encodes/decodes). This lets tests/chaos_mesh.rs exercise the SUBSTRATE
+# codec (`fountain_encode`/`fountain_decode`) directly — a real MEASURED proof,
+# not a reference stand-in.
+ciris-edge    = { git = "https://github.com/CIRISAI/CIRISEdge", tag = "v4.3.0", features = ["codec-fountain"] }
 
 # PQC realtime-A/V streaming E2E benchmark (CIRISEdge#62 realtime_av profile).
 [[bench]]
@@ -151,6 +208,13 @@ harness = false
 name = "alm_chain"
 harness = false
 
+# Sustained multi-stream seal throughput — measures the actual core-fraction to
+# seal N blob streams @30fps in a real loop (promotes the page's "2,000 blob
+# streams ≈ 6-10% of a core" from arithmetic to MEASURED).
+[[bench]]
+name = "stream_fanout"
+harness = false
+
 [profile.release]
 # panic strategy stays "unwind" (the Win7 build-std lane relies on this being
 # pinned here, not on the build-std crate list — see release.yml win7 lane).

{ciris_server-0.2.6 → ciris_server-0.3.0}/FSD/LENS_TO_SERVER_MIGRATION.md

@@ -24,6 +24,13 @@
 > (`ed25519.seed.migrated` archived), the `.rid` adopted into the keystore
 > (`hardware_backed=true`), no re-key. Adoption is deterministic: the carried
 > identity reproduces byte-for-byte.
+>
+> **Trace import re-validated** (2026-06-16, on the v8.2.0 / edge-v4.2.0 / CEG-RC12
+> floor): `import-traces` on the prod dump → 12,165 traces → 20,959 events,
+> errored=0 (3,635 salvaged). **All cutover gates are met — this migration is
+> READY:** identity continuity (byte-identical `key_id` + RNS dest), 100% hybrid PQC
+> signing, six-key `/v1/identity`, the frozen read endpoints, and legacy-history
+> pre-seed all proven on the shipped floor.
 
 ## 1. What changes
 
@@ -40,10 +47,54 @@
 manifold conformity, and the detection-event corpus all run inside the node over
 the shared substrate, queryable from any node.
 
+## 1.5 Scope correction — the three-way split + the DSAR gate
+
+> The deployed CIRISLens (`CIRISAI/CIRISLens`) serves **more than** the 7 frozen
+> read endpoints: a **DSAR** erasure surface (GDPR Art. 17 — `POST /dsar/delete`,
+> Ed25519-signed, key-scoped: *only traces signed by the requesting key are
+> deleted*), a **public-keys registry**, the **CIRIS scoring feed** (`/capacity/*`,
+> `/factors/*` — distinct from detection-event `/scores`), and **access tiers**
+> (`public_sample` / `partner_access` / `AccessLevel`). The frozen-7 alone is
+> **not** a complete replacement. Migration completeness requires all of it — but
+> it is split three ways, not absorbed wholesale into one node:
+
+- **fabric (the lens node):** the epistemic substrate — ingest, corpus, scoring
+  (emits `capacity:*`), `system:*` self-report, the **signed / key-scoped** reads,
+  the **erasure mechanism** (§19.7 hard-delete / `EjectHardDelete`), the
+  **public-keys registry**, and the **access tiers**. The fabric *performs* erasure;
+  it exposes no public hook for it.
+- **ciris-status (the monitor node):** the public aggregator + health attestor —
+  reads `capacity:*`/`system:*`, serves the public scoring + status surface
+  ciris.ai consumes, emits `health:liveness` `scores`. See
+  [`CIRISStatus/FSD/MONITORING_NODE_DESIGN.md`](https://github.com/CIRISAI/CIRISStatus).
+  The fabric node does **not** serve the public website feed.
+- **thin presentation (ciris.ai / Portal):** renders over the monitor's surface.
+
+**GDPR erasure — TWO entry points (both, not either/or), one mechanism.** Right-to-be-
+forgotten reaches the §19.7 hard-delete via **both**:
+1. **DSAR endpoint, surfaced through ciris-status** — the key-scoped, hybrid-signed
+   `dsar/delete` request (CIRISLens `accord_api.py` shape: *only content signed by
+   the requesting key is deleted*), exposed on the public monitor node (not a fabric
+   public hook), which drives the fabric's erasure; **and**
+2. **in-app, CEG-native** — the KMP fabric app lets the data subject emit a signed
+   `withdraws`/revocation against their content directly; the substrate honours it
+   via the same §19.7 descent.
+Both collapse to one substrate mechanism (revocation → `EjectHardDelete` → below the
+recoverability floor), proven by the noise-floor demonstration (CIRISServer#14).
+
+**The DSAR gate (hard).** The §19.7 erasure primitives DSAR needs
+(`evict_fountain_content_hard_delete`, `content_aggregation`,
+`EjectionVerdict::EjectHardDelete`) ship in **persist v8.4.0 / verify v5.10.0**;
+the wheel pins **v8.2.0 / v5.9.0**. **Do not decommission CIRISLens until DSAR
+works as designed on the fabric node** (substrate bump → port DSAR + public-keys
++ tiers → CIRISServer#14 noise-floor demonstration). Read-replacement (the 7
+endpoints) can swap first; the Python DSAR path stays reachable until then.
+
 ## 2. Prerequisites
 
-- **`ciris-server` is published on PyPI** (0.1.x, abi3 / CPython 3.10+: manylinux
-  x86_64 + aarch64, macOS, Windows). Substrate floor baked into the wheel:
+- **`ciris-server` is published on PyPI** (0.2.x, abi3 / CPython 3.10+: manylinux
+  x86_64 + aarch64, macOS, Windows, **Android arm64 + armeabi-v7a**). Substrate
+  floor baked into the wheel:
   **persist v8.2.0 / edge v4.2.0 / verify-family v5.9.0** (CEG 1.0-RC12).
   - **`pip install ciris-server` needs NO build deps** — the manylinux wheel
     bundles libtss2 + libcrypto (auditwheel). This is the recommended path.
@@ -125,20 +176,28 @@ replaceable default pin).
   the agent's KMP client.
 
 ### 3.5 Corpus
-The corpus **starts fresh** on the persist substrate. The legacy TimescaleDB
-history is **not migrated** (the post-cutover dedup keys differ; pre-cutover quality
-is the legacy pipeline's). Keep the old TimescaleDB **read-only** for archival as
-long as you need it, then decommission.
+The live corpus **starts fresh** on the persist substrate. **Legacy history can be
+pre-seeded** for posterity / to show the ragged edge:
+```
+ciris-server import-traces <dump-dir>     # the CIRISLens TimescaleDB dump dir
+```
+It reconstructs the flat 1.9.x `accord_traces` rows into CEG `CompleteTrace`s under
+the closed-set `2.7.legacy` schema bucket — the original 1.9.x Ed25519 signature
+preserved as **provenance**, imported **pre-verified** (`VerifyMode::TrustPreVerified`
+carve-out; the legacy sig signed the 1.9.x bytes, not the reconstruction, so it is
+not re-verifiable), content-addressed + idempotent. A salvage pass repairs the dump's
+systematic `\\"`→`\"` export mis-escaping. **Validated on the prod dump (v8.2.0
+floor): 12,165 traces → 20,959 trace-events, errored=0 (3,635 salvaged).** Keep the
+old TimescaleDB read-only until you've imported + verified, then decommission.
 
 ## 4. Verify (before tearing anything down)
-- `GET /v1/identity` (on the read-API port, `listen+1`) returns the
+- `GET /v1/identity` (on the read-API port, `listen+1`) returns the **six-key**
   `LocalIdentityAggregate` with the **same `key_id`** the CIRISLens node published
-  (identity continuity confirmed), plus the Ed25519 federation pubkey and the
-  Reticulum transport pubkeys. **0.1.x note:** `content_x25519` /
-  `content_ml_kem_768` are `null` — the content-KEM halves fill in once persist
-  exposes the aggregate for a hardware-signed Engine
-  ([CIRISPersist#223](https://github.com/CIRISAI/CIRISPersist/issues/223)); the
-  continuity-critical fields (`key_id`, `ed25519_pubkey_b64`, transport) are present.
+  (identity continuity confirmed): the **hybrid** federation signing keys (Ed25519 +
+  ML-DSA-65), the persist-minted content-KEM pair (`content_x25519` /
+  `content_ml_kem_768`), and the Reticulum transport pubkeys — **all populated** as
+  of 0.2.x (CIRISPersist#223/#224; the `with_hardware_signer_hybrid` Engine). A
+  carried-over `ed25519.seed` yields a byte-identical `key_id`.
 - Boot log shows `transport-identity keystore opened hardware_backed=true` (TPM
   host) and, for the federation key, the keyring reports a sealed-Ed25519 / hardware
   posture (not `NO HARDWARE BINDING`) — or encrypted-software fallback on a
@@ -152,6 +211,14 @@ service, the OAuth admin UI, and the prod telemetry sidecars
 (Prometheus/Loki/Tempo/Mimir/MinIO). Archive the `*.migrated-<ts>` identity files
 and the read-only TimescaleDB per your retention policy.
 
+**Gate (do NOT skip — §1.5):** decommission only after the **DSAR** erasure
+surface (Art. 17), the public-keys registry, and the access tiers run on the
+fabric node — which is gated on the persist v8.4.0 / verify v5.10.0 bump. Until
+then, keep the CIRISLens DSAR path reachable (you may retire its Grafana /
+ingest / scoring serving earlier — scoring serving moves to the ciris-status
+monitor node). Phasing: (1) read-replacement swap → (2) ciris-status public
+surface → (3) DSAR on fabric → (4) full decommission.
+
 ## 6. Rollback
 The cutover is reversible until decommission: the old deployment runs read-only
 alongside the node during the window. If the node misbehaves, re-point emitters/read