Large file: soft3/nox/audit/2026-10-17-hemera-feature-performance/era-nox.patch — 2.2 MB — the first 64 KB:
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/honeycrisp-backend.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/honeycrisp-backend.md
new file mode 100644
index 0000000..2c1e060
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/honeycrisp-backend.md
@@ -0,0 +1,42 @@
+# Honeycrisp backend: source/package contract investigation
+
+Owner: /root/phase2_resume_audit under /root; 2026-10-16. Reused owned checkout
+`nox/.worktrees/no-std-dependencies/nox`, branch `fix/honeycrisp-backend`, base
+`434d48ee7e94fdde0f4e7bb71012afb80db21a7e`. Clean/idle transition and preserved
+sibling targets are recorded by the wrapper task context.
+
+This phase writes only this plan and `audit/2026-10-16-honeycrisp-backend-design/`.
+No production edits, dependency/version changes, fallback, removal or parallel
+algorithm implementation. Root specifically prefers the existing upstream APIs
+and an owner release handoff over duplicating them in Nox.
+
+1. Bind the published acpu 0.2.0 archive/checksum/VCS identity, actual exports,
+ Nox callers and canonical Honeycrisp source to exact revisions and hashes.
+2. Inspect the established NTT and multilinear contracts, including coordinate
+ order, root direction, normalization, noncanonical residues, budget and trace.
+ Distinguish source defects from absent registry delivery and stale AMX/Metal
+ descriptions. Inspect existing unmerged validation fixes without adopting them.
+3. Reproduce the current registry-feature failure. In a separate temporary
+ diagnostic crate, explicitly patch only acpu to the canonical source; keep its
+ generated lock outside the repository and record the full resolution identity.
+ Check the Nox feature and existing upstream arithmetic using independent u128
+ DFT/hypercube-sum references, then backend result/budget/trace equivalence.
+ This source diagnostic is never a registry gate or a production input.
+4. Run acpu packaging as a read-only source probe with an external cache. Record
+ normalization/verification or the exact first packaging blocker; never change
+ its manifest or lock to manufacture a package. Preserve all red evidence.
+5. Return a compact source/package design and minimal owner action. A future
+ implementation/release requires separate review; do not claim performance,
+ certification, release readiness or publication from these diagnostics.
+
+Verification questions: Are the symbols renamed or unpublished? Does the source
+implement the same field/order convention? Does Nox actually consume their
+outputs correctly? Can the normalized package build against declared registry
+dependencies? Does any proposed repair add an unnecessary implementation?
+
+Investigation complete: unpublished APIs confirmed; source debug/release and
+normalized-package diagnostics pass the independent arithmetic and Nox backend
+checks. Prefer an upstream acpu-only 0.2.1 proposal with explicit package-version
+approval, then a Nox registry-lock update after owner publication. No Nox runtime
+repair is justified by the missing symbols. Whole-upstream release gates remain
+unrun; see the audit for exact identities, results, caveats and owner handoff.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/published-api-baseline.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/published-api-baseline.md
new file mode 100644
index 0000000..40c86cb
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/published-api-baseline.md
@@ -0,0 +1,65 @@
+# Published-archive API companion
+
+Base `102b9e3ee35921f2289db6e87ce3182cb06946b3`, branch
+`fix/published-api-baseline`, reused owned `no-std-dependencies/nox` checkout.
+The previous wrapper context is archived in
+`audit/2026-10-17-published-api-baseline/task-honeycrisp-backend.json`.
+Hemera `1c385e54`, Strata `56aedb2d` and Lens `8b26cef6` symlink targets/revisions
+remain unchanged. Builds use an external task cache; no production inputs change.
+
+## Authority and scope
+
+The required exact locked v0.2.0 tag gate remains unchanged and red. Its existing
+research explicitly withholds policy-change authority. This task creates an
+executable companion diagnostic and a concrete policy proposal for owner review;
+no successful companion result can replace, waive or mark that gate green.
+No dependency/version edits, source substitutions, tags or publication actions.
+Scope is Nu/Rust tooling, fixture inputs, this proposal and audit evidence.
+
+## Evidence design
+
+1. Fetch the official `cyber-nox 0.2.0` index record and crate archive into the
+ task cache; verify archive SHA256
+ `7c807c1b53e66cea79e8e130ca938450029af3f096984a2839fee6443a171b3f`.
+ Record exact acquisition argv/status and the archive's `.cargo_vcs_info.json`.
+ Compare owning Rust bodies with the peeled immutable v0.2.0 source, explaining
+ Cargo normalization and the published lock separately. Preserve the tag and
+ original locked-tag failure; do not regenerate its lock.
+2. Produce baseline and current rustdoc JSON in distinct source/target roots
+ with the same pinned compiler and flags. The baseline is the unmodified
+ published archive. The current side is an exact normalized package of the
+ committed owning source, retaining registry dependency identity; verify its
+ Rust bodies equal the owner. The current occupied version is diagnostic only.
+ Record all package manifests, locks, source/artifact hashes and actual commands.
+3. Build default (empty crate defaults) and explicit-std API surfaces separately using
+ `cargo rustdoc --locked --offline` and explicit JSON output. Use installed
+ pinned rustup 1.95.0 with the documented rustdoc JSON mechanism, and installed
+ `cargo-semver-checks 0.51.0` with explicit `--baseline-rustdoc` and
+ `--current-rustdoc` paths. Predeclare patch-compatible comparison; report the
+ actual verdict, counts and omissions. Never allow automatic shared-target
+ baseline discovery. Any tool/format failure stays a failure.
+4. Independently inspect resolved feature graphs: old default Hemera/std,
+ repaired default without it, and explicit std forwarding in both surfaces.
+ Name transitive std-only APIs and actual dependency versions. The public API
+ tool does not adjudicate this compatibility change; neither does a default
+ API pass determine Nox's release version. Optional backends remain outside
+ this companion's acceptance claim, with their existing delivery debts named.
+5. Write a portable verifier for acquisition/source/artifact/raw-stream hashes,
+ exact commands/tool identity and separate roots. Keep bulky rebuildable
+ artifacts in the external cache; retain the minimal reproducible source,
+ artifact identity and raw verdict evidence under the owning audit.
+
+## Proposed policy, not adopted
+
+For a future owner decision, distinguish source-tag reproducibility from the
+public compatibility of bytes actually distributed by crates.io. A published
+archive comparison could become an additional required compatibility gate when
+its checksum, VCS correspondence, dependency domain and feature surfaces are
+verified. The exact locked-tag failure remains a separate unresolved release
+gate until the owner explicitly decides its policy; no retrospective repair of
+the tag is proposed. State this separation in the machine-readable outcome.
+
+Acceptance for this task: genuine old/current artifacts, executable comparison,
+independent feature-inheritance findings, preserved historical red and a reviewable
+policy proposal. Root reviews this plan before tool implementation; final CODE
+review and source-bound evidence precede an ordinary tooling commit.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/release-hygiene.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/release-hygiene.md
new file mode 100644
index 0000000..9b8600c
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/plans/release-hygiene.md
@@ -0,0 +1,43 @@
+# Nox release hygiene
+
+Root authorized on 2026-10-16 after read-only Kadek prerequisite audit. Agent:
+/root/phase2_resume_audit; shared parent /root. Base/pushed master:
+7fe9ad368dc93ef136c196c2366b39f1c67e1cd7. Reuse the clean idle checkout
+nox/.worktrees/no-std-dependencies/nox on new branch fix/release-hygiene.
+Prior source-decision task and audit remain intact. Before reuse, tracked,
+untracked and ignored status were empty; lsof showed only the inspection itself.
+The wrapper's historical context is retained alongside the new context.
+
+Implement only the mechanical cargo-fmt delta (44 files measured in canonical
+Nox), CLI parse_data's redundant &formula_text, and strict-rustdoc markup in
+call, patterns/{eq,look}, trace, parallel, jets/{registry,merkle_verify,backends/cpu}.
+Do not change runtime algorithms, dependency manifests/versions/lock, optional
+backend behavior, expected test values/literals, API-baseline policy or benchmark
+harness logic. Test syntax changes are limited to the explicit extension below.
+Existing oversized modules remain a separately reported quality obligation;
+this bounded unit does not introduce structural refactors to conceal it.
+
+Root approved a precise extension after initial strict Clippy exposed three
+test-only lints: both fixed-modulus `(p + 1) / 2` expressions become
+`p.div_ceil(2)`; the pure filtered trace iterator's `last()` becomes `next_back()`.
+The odd modulus is `0xffff_ffff_0000_0001`, whose increment fits u64, so both
+halves equal `9223372034707292161`. Clippy then required the equivalent
+`rfind` spelling of the same pure reverse predicate; root approved this final
+syntax. Expected values/assertions remain unchanged.
+Preserve initial red and its source identity; final receipts use a new manifest.
+
+Preserve sibling symlink targets and committed inputs: Hemera
+1c385e54e18885075f0dd12a0407ad0234e1bebf, Strata
+56aedb2d12b3126c601eb333419136d403614dbb, Lens
+8b26cef6587bee6a686f2cf163f6a8496931ee6a. Record hashes before edits and before/
+after each gate; use external ~/.cache/cyber/kadek/nox-release-hygiene.
+
+Validate pinned rustup1.95 default/core/workspace tests, real thumb codegen,
+fmt, strict workspace/all-target Clippy and rustdoc, verified packaging and
+normalized-package thumb. Compare a mechanically formatted pristine source
+export with the candidate to isolate exact non-format changes. Retain genuine
+failures; no fixes outside this scope without root direction. Honeycrisp/ring/
+performance and owner-only version/tag/publication obligations remain open.
+
+No commit until root reviews the exact source diff and gate receipts. Retain
+checkout through integration, then inspect all file classes before disposal.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/exact-tag-api-baseline/research.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/exact-tag-api-baseline/research.md
new file mode 100644
index 0000000..603b795
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/exact-tag-api-baseline/research.md
@@ -0,0 +1,19 @@
+# Restore an executable exact-tag API baseline
+
+Stage: blocked; evidence: measured. Discovered-from: [Hemera no_std
+repair](../hemera-no-std/research.md). Serves nox release/API conformance under
+cyberia/dev § rings. Blocks: clean last-tag gate and any claim of clean release
+validation; does not replace existing authorization for the bounded decision PR.
+
+At owning source 0b1407a4b855e4961ede07e1b7ea199cb8018c30, the exact v0.2.0 tag
+b927873bf6eb9296877b0fb3abb6607c353d31a6 has Cargo.lock entries for nox0.1.2,
+Hemera0.3.0, Lens-core0.1.1 and older Strata while its manifest declares nox0.2.0.
+Record64's real isolated `cargo rustdoc --locked --offline` fails first:
+`error: cannot update the lock file /tmp/nox-no-std-inputs/nox-tag/Cargo.lock
+because --locked was passed to prevent this`.
+
+No historical tag or lock is modified. A generated standalone harness can provide
+a separately labeled API diagnostic, but cannot turn this exact locked gate green.
+A follow-up must determine the canonical historical source/dependency delivery
+contract and review an explicit baseline policy before changing the required gate.
+No policy change or release action is authorized by this task note.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/execution.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/execution.md
new file mode 100644
index 0000000..70343f7
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/execution.md
@@ -0,0 +1,72 @@
+# Hemera feature-boundary execution
+
+Approved input: PLAN v2 `1f2028db98726cea04732856de00b2b058501b930112df0811f09c83c1ac60d3`.
+Fresh Opus 5 APPROVE completed `2026-10-13T02:23:59.183394Z`; raw stdout
+`1bd21c68c348163df8bd58a0205772732e50dfc733d30374aa61cdf88d09c223`.
+Invocation/completion/full raw are retained in
+[audit review](../../../audit/2026-10-13-hemera-no-std/review/plan-v2/stdout.json).
+Root read/accepted this exact plan and authorized the two-file implementation.
+
+Historical PLAN inputs remain unchanged. All parent commands completed before the
+production edit, including extra records 68–71: normalized-package thumb build
+fails on Hemera/std, while parallel/brakedown/wgpu inverse feature trees succeed.
+This supplements the 67 frozen PLAN records, not a retroactive PLAN measurement.
+
+Adopted advice: side-by-side default/std trees plus existing variants, durable PR
+names for the two std-only Hemera APIs, a named exact-tag gate follow-up, and the
+verbatim delivery boundary: Kadek still resolves unchanged registry nox 0.2.0.
+The optional install hint is omitted to keep the approved gate delta exact; the
+gate already states its target prerequisite. No toolchain is installed.
+
+The review's approval concerns this source repair only. Consumer findings are
+manifest/source evidence, not full product builds; dependency std API behavior is
+outside cargo-semver-checks' model. Existing user authorization covers ordinary
+source merge with decision disposition, never publication/version/tag/release.
+Candidate results are pending at this execution note's initial creation.
+
+## Measured candidate and retained reds
+
+The candidate exactly matches the two approved proposed files; 48 owning Rust
+files, all sibling source and all source locks remain byte-identical. Candidate
+exports use `/tmp/nox-no-std-candidate-inputs`; parent and candidate compiler roots
+are distinct, recorded per command. Records 72–101 are the scoped candidate gates;
+102/103 are the single predeclared paired benchmark repeat.
+
+- Actual no_std code generation passes in both sibling-source (72) and normalized
+ package (96) epochs; their exact parent builds fail at Hemera `extern crate std`
+ (38/68). Default inverse tree (90) has no Hemera std feature; explicit std (91)
+ and parallel/brakedown/wgpu (92–94) do. No dependency was removed or substituted.
+- Workspace debug/release and std each pass 161 owning tests (74–76);
+ parallel/brakedown each pass 164 (77/78). Nightly-2025-11-26 invocation82 succeeds
+ with zero doctests; it is not extra behavioral coverage. CLI build/test and wgpu
+ check pass, with zero CLI tests. Existing four H264 controls pass debug/release
+ against both sibling and package dependency domains (84/85 and98/99); package
+ library tests97 pass161. All counts name their raw record and exact frozen source.
+- Current-parent default-surface API comparison101 passes229 checks, skips31,
+ consuming the two exact JSON files recorded by63/100 from distinct compiler
+ targets. No claim is made about dependency feature API inheritance by that tool.
+ Exact-tag gate64 remains unmet; [follow-up](../exact-tag-api-baseline/research.md)
+ owns the explicit blocks edge. Automatic diagnostics60/61 remain unaccepted
+ shared-target evidence, not substituted for the valid JSON comparison.
+- Required inherited reds remain: fmt79 equals parent58 after only path-prefix
+ normalization; strict docs81 has the same error headings as47; honeycrisp89 has
+ the same missing-acpu-symbol errors as56. Clippy80 and57 have the same
+ needless_borrow source diagnostic at cli/main.rs:247:52, but Cargo's final wrapper
+ differs (`bin nox test` versus `bin nox`); full stream identity is not claimed.
+ Parent Trident59 stops at cached clap4.5.57; no candidate product build is claimed.
+- Performance is red/unverified, not inherited-green and not explained away as
+ noise. Initial comparison49/83 has five cases crossing the plan's threshold;
+ one paired repeat102/103 has six. Repeat medians include tree+89.64%, particle
+ +43.12%, hash-chain+46.90%, hash+5.28%, inv+21.08%, look+15.82%; add and mul reverse
+ direction versus the first pair. Raw estimates, samples and both comparisons are
+ retained. The shared host was not a controlled benchmark lab. Root paused its
+ heavy Cargo work during the repeat and this agent ran no concurrent compilation;
+ other system activity/frequency was not measured. Cause is unestablished. No
+ further repeat or source tuning is hidden. Post-repeat binaries have equal
+ 3028144-byte size but different full-file SHA-256; this does not establish emitted
+ code equality or identify a performance cause.
+
+Ring1/decision remains necessary. No whole-product, clean release, speedup or
+registry-delivery claim follows. The PR must state the two affected dependency
+APIs (`Hash::to_hex`, `Read` for `OutputReader`) and the future graph/feature-aware
+release floor. Kadek still resolves unchanged registry nox 0.2.0.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/feature-audit.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/feature-audit.md
new file mode 100644
index 0000000..bf9aed0
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/feature-audit.md
@@ -0,0 +1,71 @@
+# Feature reachability at the pinned sources
+
+Scope: nox `0b1407a4b855e4961ede07e1b7ea199cb8018c30`, Hemera
+`d5f0a09539360934fb32db9b2e15a91995607db6`. Generated evidence is
+`feature-audit/{hemera-cfg-sites,reverse-feature-audit,reverse-api-scans}.json`;
+`feature-audit.rb` scans the complete committed `.rs`/`.toml` inventory, retaining
+full source hashes and exact line text. This is source/manifest analysis, not a
+claim to have built every consumer.
+
+## Hemera
+
+All three `std` cfg sites are: `rs/src/lib.rs:54` (`extern crate std`),
+`sponge.rs:37` (`Hash::to_hex`), and `sponge.rs:462` (`std::io::Read` for
+`OutputReader`). The latter two are real dependency API changes when its std
+feature is no longer unified on by another edge. `Hash`'s Display and
+`OutputReader::fill` remain unconditional. Tests' explicit std imports are under
+`cfg(test)` and do not affect nox's dependency build. The two async module guards
+in `lib.rs:78,80` are controlled by `async`, whose feature forwards `std`; nox
+never enables async. Serde is likewise unchanged and not enabled by nox.
+
+All fourteen `hemera_portable` cfg/cfg_attr sites are architecture decisions,
+independent of std: `arith.rs:61,95,131,141,178,191,220,229,261` and
+`backend.rs:85,101,133,146,178`. The first arith site only permits dead code on
+aarch64. The others select register-only aarch64 arithmetic or portable Rust;
+`Cargo.toml:22` additionally registers the cfg name for linting. There is no
+runtime CPU-feature detection in the committed Rust source. Disabling std does
+not select a different arithmetic backend. `profile.rs` and `kernel.rs` have no
+std/portable feature guards. Public-data and constant-time kernels remain
+selected by the existing hash entry points, independent of std.
+
+Nox uses `tree::{hash_leaf,hash_node}`, `Hash::{from_bytes,as_bytes}` and
+`StepSponge`/Hemera Goldilocks. The complete `git grep` evidence covers owning
+Rust, including benchmarks and tests. None calls either std-only API. Its
+public digest/particle values are NeBu arrays or byte arrays, not a re-export of
+Hemera's std-only methods. Architecture arithmetic is reachable through hashing,
+so the named reduction benchmark still runs on both parents/candidates; source
+independence alone is not used as a performance gate waiver.
+
+## Named reverse consumers
+
+Exact manifests and all `hemera::`, `to_hex`, `OutputReader` Rust matches are
+retained. The source revisions below are historical exact inputs, not dirty
+working trees. Each direct Hemera path resolves to the same sibling location
+as nox's edge in its stated layout.
+
+| Repository and revision | Manifest-level Hemera/std inheritance after the proposal |
+| --- | --- |
+| soft3 `44824e6cf64f5b0b1d7443eea412001e74c5f32e` | `conformance/rs/Cargo.toml` independently enables Hemera defaults; nox also requests brakedown → std. |
+| zheng `5733dfdcc15cbc22fce9f5877b37515d005b8c44` | Both `rs` and `cli` independently enable Hemera defaults and request nox/brakedown → std. |
+| mudra `186c0f22871e72ac5d27396d893998865fc604d4` | Root manifest independently enables Hemera defaults; optional nox/proof activation does not remove that edge. |
+| bbg `441e3c9ddf85c4bee36b40ed7ae8805b1481bc27` | `rs` independently enables Hemera defaults, regardless of its default nox edge. |
+| Trident `ec986d8edb926da51a70c23c97782d65a239c144` | Root manifest independently enables Hemera defaults. Standalone `silicon` declares no direct Hemera dependency and has no `hemera::`/`OutputReader`/Hemera `to_hex` use; its `compile_to_hexagon` names are unrelated. Both manifests request unavailable path nox ^0.3.0 while this nox is 0.2.0. |
+| nox CLI at the owning parent | No direct Hemera dependency or affected API use; its actual build/test is included in owning workspace and separate CLI controls. |
+
+These manifests establish the local additive-feature facts; they do not prove
+complete graphs, locks, target variants or product execution. Actual build/test
+of soft3, zheng, mudra and bbg, and Trident product build/test remain unverified.
+The isolated locked Trident metadata probe (record 59) first fails on missing
+cached clap 4.5.57; the nox version mismatch is separately source-proven, not its
+observed first error. Kelvin drift/rung specification checks remain unverified.
+
+## Ring and delivery
+
+The pinned registry identifies nox as layer 1's machine, with Hemera and Strata
+`part_of = nox`, and Trident as layer 2's direct dependent. The reverse Cargo
+edges above extend the blast radius beyond this repository. This is ring 1,
+with `decision` disposition because rung/product gates are not all green. The
+session's existing owner instruction authorizes ordinary source work/review/
+merge; it does not authorize publication, a bump, tag or release. The expected
+patch result of an owning default-surface API comparison is not a declaration
+that the full graph's release floor is patch.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/plan.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/plan.md
new file mode 100644
index 0000000..d44b02c
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/plan.md
@@ -0,0 +1,136 @@
+# Preserve nox's no_std dependency boundary
+
+Stage: revised PLAN v2, awaiting fresh different-vendor review. Parent:
+`0b1407a4b855e4961ede07e1b7ea199cb8018c30`. Lineage and measured failures are
+in [research.md](research.md); exact feature/ring analysis is in
+[feature-audit.md](feature-audit.md). [review-v1.md](review-v1.md) disposes the
+first review. No production change before fresh approval.
+
+## Exact change and durable guard
+
+In `rs/Cargo.toml` only these two values change:
+
+```diff
+-std = []
++std = ["hemera/std"]
+@@
+-hemera = { package = "cyber-hemera", version = "0.3", path = "../../hemera/rs" }
++hemera = { package = "cyber-hemera", version = "0.3", path = "../../hemera/rs", default-features = false }
+```
+
+Add a project-specific `no_std dependency gate` section to `CLAUDE.md`, naming
+this executable every-commit gate, requiring an installed thumb target and the
+repository's normal committed sibling layout:
+
+```sh
+cargo build -p cyber-nox --no-default-features --target thumbv7em-none-eabi --locked
+```
+
+Run from the repository root. CI remains unchanged; the named repository gate
+is durable and code-generates the real library. Local evidence additionally uses
+`--offline` and an isolated checksum-verified source cache. Do not install a target
+silently when it is absent; record a missing prerequisite as a red gate. No new
+script or runtime dependency is necessary.
+
+With nox defaults disabled, the nox edge no longer enables Hemera/std. Explicit
+nox/std forwards it; parallel/brakedown/wgpu/honeycrisp already include nox/std.
+Other dependency edges can still independently enable Hemera/std. The two std-only
+Hemera APIs and every architecture cfg site have been audited; source selections
+for arithmetic are independent of std. All paths, versions, optionality, type
+identities, Rust source, locks, CLI manifest, algorithms and canonical specs stay
+byte-identical. Only the manifest and named gate declaration are production scope;
+task/audit evidence is separate. No loose audit file is named Cargo.toml.
+
+## Steps → verification
+
+1. Freeze parent, sibling exports, registry checksums, toolchain and tag → verify
+ complete Git body/mode/link inventories. Retain all failed harness attempts.
+ Measure each introduced command at the parent before changing production,
+ including workspace debug/release, owning std/parallel/brakedown, docs, pinned
+ nightly doctests, format, Clippy, reduction benchmark, CLI, H264 and package
+ variants. Existing results remain attributed to their actual revision/command.
+2. Apply the exact manifest and gate declaration after approval → verify only those
+ intended bytes differ. Candidate exports preserve all other frozen input bytes.
+ Parent/candidate/package/nightly/compiler JSON builds use distinct actual
+ compilation roots. Pin toolchain-bin PATH as well as RUSTC/RUSTDOC, avoiding
+ mixed Homebrew/rustup Clippy drivers. Two jobs; incremental disabled.
+3. Build actual no_std library → the named thumb build, host no-default-features
+ check, and normalized-package thumb build must pass. The parent thumb failure
+ is specifically Hemera `extern crate std`. Inspect default feature metadata
+ and explicit std inverse tree: default must exclude Hemera/std; std must include
+ it. Do not suppress a dependency, target or real kernel to obtain green.
+4. Preserve behavior → repeat exact parent workspace debug/release and owning
+ std/parallel/brakedown tests, CLI build/test, wgpu check, honeycrisp check, and
+ the four actual Kadek H264 literal/error/resource tests in debug/release.
+ Honeycrisp currently resolves acpu but fails on its absent `ntt_forward` and
+ `multilinear_eval` functions; preserve that inherited result, not an obsolete
+ cache-unavailable claim. These controls do not represent the whole Kadek suite.
+5. Run the named `reduction` benchmark in parent/candidate under the same compiler,
+ flags, two jobs, no incremental, target architecture and Criterion settings:
+ `cargo bench -p cyber-nox --bench reduction --locked --offline --
+ --warm-up-time 1 --measurement-time 2 --sample-size 20 --noplot`.
+ Preserve all nine estimates/samples, compare per-case confidence intervals and
+ relative point estimates, record environment/concurrent-load limits. A measured
+ regression or indeterminate noisy result is an explicit red/unverified gate,
+ not waived because algorithms are unchanged. Investigate a >5% median slowdown
+ or disjoint slower confidence interval with one paired repeat before attribution;
+ do not promise a speedup or alter Rust to tune this manifest fix.
+6. Check distribution without releasing → `cargo package -p cyber-nox --no-verify
+ --locked --offline --allow-dirty`, inspect the normalized manifest and generated
+ package lock. External paths are removed by Cargo, not production edits. Package
+ Rust must equal owning source. Test the extracted library on host and build it
+ for thumb. Repeat the same H264 literals using registry NeBu 0.1.1 matching the
+ package in a separate nonmember harness/target. Measure its parent first: any
+ already-present literal/overflow error belongs to that registry dependency
+ epoch, not this feature patch. Do not normalize production NeBu to repair it.
+7. Repeat format, workspace/all-target Clippy `-D warnings`, owning docs with
+ `RUSTDOCFLAGS=-D warnings`, and actual nightly-2025-11-26 doctests. Compare exact
+ first errors and error sets with parent. Preserve unrelated format, CLI lint,
+ docs, optional-backend and package-epoch reds; no unrelated source edits.
+8. Owning API → compare current parent/candidate default surface through separately
+ emitted, hashed JSON from separate actual rustdoc targets; expected surface
+ floor is patch. Attempt the exact-tag v0.2.0 locked baseline; its committed lock
+ presently requires an update (record 64), so this required gate is unmet. An
+ alternate generated-lock tag comparison, if retained, is diagnostic only and
+ never substitutes for that red. Automatic runs 60/61 returned pass but reused a
+ compiler target, so are not accepted as isolated proof. No 26-crate API rerun.
+9. Close the ring honestly → keep each named reverse-consumer feature audit,
+ isolated Trident prerequisite, all unexecuted product/build/test/spec/Kelvin
+ obligations explicit. No sibling normalization, product bypass, fleet effects
+ or release action. Freeze final source, exact commands/raw streams, benchmark
+ samples, known reds and feature/API limits for fresh CODE review and portable
+ Nu replay. Root owns explicit staging/ordinary merge.
+
+Targets stay below 20 GiB, staging below 30 GiB. Reuse source-identical parent
+results when appropriate, without claiming a different command or environment was
+run. Registry archives and available toolchains are fixed; no installation is part
+of this plan. Nu verifies the portable audit; historical Ruby capture scripts remain
+evidence and do not become repository tooling dependencies.
+
+## Five likely failures
+
+1. Lost inherited Hemera/std affects APIs or backend performance → enumerate its
+ three std API/linkage guards and fourteen architecture guards; audit every named
+ consumer's feature inheritance; execute paired reduction and std feature checks.
+2. no_std is only a host illusion → real thumb code generation in sibling and
+ normalized-package epochs plus the named durable repository gate.
+3. Delivery accidentally changes identity or hides older NeBu behavior → keep all
+ production paths and pins, compare package metadata, measure registry H264
+ separately, preserve any pre-existing overflow/literal errors.
+4. Environment/cache drift disguises a red → checksum-pinned inputs, source
+ before/after proof, toolchain-bin PATH, separate parent/candidate/rustdoc roots;
+ all new gates have exact parent baselines, including harness failures.
+5. Local success becomes a false delivery/phase claim → ring 1 and `decision`,
+ product/Kelvin and exact-tag reds explicit. Kadek still resolves unchanged
+ registry nox 0.2.0. Owner-only publication/version delivery and separate Kadek
+ alloc/math/public selector work remain open.
+
+## Acceptance and remaining obligations
+
+Accept the scoped source repair only with real no_std passes, no unexplained new
+failure, required paired evidence and fresh CODE approval. It is not a clean ring-1
+candidate. Existing owner authorization covers ordinary implementation/review/merge;
+`decision` and any required `wip:` label record the retained reds rather than creating
+another permission request. No version, tag, registry publication or release is
+performed. Future release floor includes the graph and inherited dependency-feature
+contract, beyond cargo-semver-checks' default-surface result.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/research.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/research.md
new file mode 100644
index 0000000..23afc96
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/research.md
@@ -0,0 +1,130 @@
+# Hemera feature propagation
+
+Stage: active research. Serves the owner's Kadek phase-1 foundation closure,
+through nox's declared `no_std + alloc` mode and Kadek foundation row 7's real
+scalar kernels. Discovered from Kadek private FLAC header audit, PR 60, merged
+as `b939c75e553bc7d8c645216555e8d80d20f3d950`. Public FLAC selection follows.
+
+Owning nox parent is origin/master `0b1407a4b855e4961ede07e1b7ea199cb8018c30`.
+Worktree: `nox-no-std-dependencies`, branch `fix/no-std-dependencies`. No production
+change has been made. `rs/lib.rs:15` already selects no_std when `std` is disabled.
+But `rs/Cargo.toml` enables Hemera defaults unconditionally; Hemera's default
+includes `std`. Cargo features are additive: Kadek's existing
+`nox default-features=false` cannot remove a feature enabled by this dependency.
+
+## Exact inputs and observations
+
+Research commands and full streams are frozen under the research evidence's
+`records/NN-*/`. Two wrapper versions are retained; the later one selects a private
+registry and explicit Rust 1.95.0. Both use two jobs and no incremental compilation.
+
+| Input | Exact revision |
+| --- | --- |
+| nox origin/master | `0b1407a4b855e4961ede07e1b7ea199cb8018c30` |
+| Hemera origin/main | `d5f0a09539360934fb32db9b2e15a91995607db6` |
+| Strata origin/main | `494df7a0973ae10a6cc1c2022e644d70449a29d6` |
+| Lens origin/master | `8b26cef6587bee6a686f2cf163f6a8496931ee6a` |
+| Kadek control source | `b939c75e553bc7d8c645216555e8d80d20f3d950` |
+
+Records 02–04/08 retain live `git ls-remote --symref origin HEAD` results.
+`committed-inputs.json` verifies every mode, blob and body/link target of isolated
+Git exports: 143/100/244/49 entries respectively. These exports, not original
+sibling working trees, are Cargo inputs. Registry material is extracted from 186
+locally cached crate archives whose SHA-256 matches the exact lock/index entry;
+all unpacked file hashes and directory-source configuration are retained. No
+upstream code, package checksum, compiler or dependency setting was edited.
+
+- Records 09/10 first failed during resolution: the old shared directory cache
+ lacked optional `acpu`. These are prerequisite failures, retained unchanged.
+- Record 11 runs exact-parent `cargo check -p cyber-nox --no-default-features
+ --target thumbv7em-none-eabi --locked --offline` with the isolated manifest.
+ It fails with `error[E0463]: can't find crate for std` at the committed Hemera
+ `rs/src/lib.rs:55`, before nox builds. Record 17's inverse feature tree names
+ nox → Hemera/default → Hemera/std directly.
+- Record 13 runs `cargo test -p cyber-nox --lib --locked --offline` against these
+ same committed siblings: 161 pass, zero failures or ignored cases.
+- Records 15/16 run the actual Kadek H264 formula and scalar adapter against this
+ nox and the same path NeBu. Four tests pass: three unchanged literal/error tests
+ extracted from the committed integration test plus the unchanged resource test.
+ Record 15 creates the external nonmember harness lock offline; 16 repeats it
+ locked. This is a bounded kernel control, not the full Kadek workspace or its
+ independent FFmpeg vector suite. Harness source and extraction provenance are
+ explicit, with no mock nox implementation.
+
+## Packaging and delivery are distinct
+
+Record 12 runs `cargo package -p cyber-nox --no-verify --locked --offline
+--allow-dirty` in the isolated exact-parent export. Cargo creates a local archive
+with 52 files. Its normalized manifest already removes all external path keys
+while retaining the published version requirements. Its generated lock resolves
+registry NeBu 0.1.1, Hemera 0.3.1, lens-core 0.1.2 and lens-brakedown 0.1.1.
+Record 14 checks that extracted archive for thumb and reproduces the same first
+Hemera `std` error. Thus the packaging route is real; a successful local archive
+after the proposed fix will be evidence, not a publication or release candidate.
+
+The registry index acquired in record 01 lists nox only through 0.2.0. Every
+published version enables Hemera defaults. The current nox origin's 48 Rust files
+match the published 0.2.0 source in 46 files; the two remaining jet diffs contain
+comments only. This does not make current siblings identical to registry sources:
+Hemera has implementation changes, and current NeBu includes a Dot overflow fix
+absent from published 0.1.1. The existing path identity must remain intact.
+
+A direct Git dependency on nox remains unavailable because its four external
+sibling paths are not within the fetched repository. Normalizing those paths in
+production was considered and rejected: CLI and real soft3, zheng, mudra and bbg
+consumers share path NeBu values with `Reduction::atom(Goldilocks)`. Switching only
+nox to registry NeBu creates a new type-identity break. Committed consumer manifests
+and concrete exchange excerpts are retained. Trident independently already requests
+nox 0.3.0 while this origin is 0.2.0; that is not a reason to introduce another break.
+
+The minimal upstream repair is therefore feature propagation only. Delivery to
+Kadek waits for an owner-authorized version/release/publication action; no such
+action is part of this unit. An upstream source merge alone does not fix Kadek's
+locked registry dependency. A later Kadek alloc/math unit can be reviewed separately
+while keeping its thumb gate explicitly blocked on this dependency delivery.
+
+## Limits and follow-up
+
+Kadek-ref itself lacks `#![no_std]`; its VLC tables and transforms use Vec, and
+transforms call std-only sin/cos/sqrt methods. No kernel may be hidden to make the
+gate pass. Explicit alloc imports and a reviewed portable math boundary are the
+separate next owning change; libm precision must be assessed against existing
+contracts and literals. This research does not change float algorithms or claim
+full runtime conformance. Physical-memory/pinning policy remains untouched.
+
+Nox's committed CLAUDE requires clean tests/type checks/lints and preserves manifest
+discussion; root has accepted this narrow feature-only scope for formal PLAN.
+The current dev doctrine requires fresh different-vendor PLAN and CODE reviews,
+the last-tag API gate and ring-aware evidence. Nox is the layer-1 machine; registry
+`part_of`/dependent obligations are retained. No release-train component version,
+pin, tag or frozen default branch is modified. Product/consumer gates that cannot
+run from exact inputs must remain explicitly unverified, never relabeled green.
+
+## PLAN-review correction evidence
+
+The first review requested feature reachability, durable no_std coverage, benchmark
+and ring/baseline precision. See [review-v1.md](review-v1.md) and
+[feature-audit.md](feature-audit.md). Their exact commands and complete streams are
+new records 19–67; v1's frozen source/records are unchanged.
+
+The corrected parent matrix measures workspace debug/release, std, parallel,
+brakedown, pinned-nightly doctests, CLI build/test and wgpu check successfully. The
+nine-case reduction benchmark completes with all estimates/samples retained. Both
+source and packaged-source H264 controls pass four tests in debug and release;
+normalized-package library tests pass 161. These are parent controls, not a fixed
+no_std candidate. The real thumb build still fails at Hemera's `extern crate std`.
+
+Inherited first errors: format check reports existing formatting differences;
+correct-driver Clippy reports needless_borrow at cli/main.rs:247; strict docs
+report unresolved `11` at rs/call.rs:47; honeycrisp reports missing
+acpu::field::ntt_forward at rs/jets/backends/honeycrisp.rs:85. Trident's actual
+locked metadata fails first on unavailable cached clap 4.5.57. Tag v0.2.0's real
+locked rustdoc build fails because its committed Cargo.lock requires update.
+Each failed gate retains its exact full output, not just this summary. No fix to
+these unrelated sources/locks is proposed.
+
+API automatic parent/tag diagnostics return 229 pass/31 skip but share an actual
+compiler target, violating this task's isolation rule; they are not accepted proof.
+Separate current/parent rustdoc JSON builds exist with distinct targets and hashes.
+The tag locked failure remains the required gate result. A release API floor or
+complete product/phase acceptance is not claimed.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/review-v1.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/review-v1.md
new file mode 100644
index 0000000..9ed27f2
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/.claude/tasks/hemera-no-std/review-v1.md
@@ -0,0 +1,58 @@
+# PLAN v1 disposition
+
+Opus 5 returned REQUEST CHANGES at `2026-10-13T02:01:04.647084Z`.
+Exact input: 130675 bytes, SHA-256
+`3b17ac27ecf44c2e211f1e87a14f0f914825b53aabac6f488862f9cc701e9ea4`.
+Raw stdout JSON SHA-256:
+`77ffab3cddb12497fe1468751032b67b583f18671a28ef51843e855c0e93e400`.
+Original input, invocation, completion, stdout/stderr and portable v1 capsule remain
+unchanged. This disposition is new evidence; it does not retroactively amend v1.
+
+1. Accepted: missing Hemera cfg/API/backend analysis. The complete 18-site inventory
+ is now retained (three std, fourteen architecture guards, one lint declaration).
+ Hash::to_hex and OutputReader's Read implementation are actual conditional APIs;
+ architecture selection has no std guard. Reachability and source scan limits are
+ explicit in feature-audit.md.
+2. Accepted: repository benchmark gate was omitted. Actual parent record 49 measures
+ all nine reduction cases with the declared Criterion settings. Candidate uses
+ the same settings; raw estimates/samples and a bounded paired-repeat policy are
+ required. Algorithm identity is not a gate waiver.
+3. Accepted: reverse consumers need feature inheritance, not only NeBu identity.
+ The named exact manifests independently preserve Hemera defaults; isolated
+ nox-cli/Trident-silicon have no affected direct API use. Product execution remains
+ explicitly unverified, despite the manifest-level findings.
+4. Accepted: durable no_std guard missing. V2 proposes a project-specific CLAUDE
+ gate using real thumb `cargo build`, measured on the exact parent in record 38.
+ No new script or CI dependency layout is introduced.
+5. Accepted: ring/decision ambiguity. Computed ring is 1; product/Kelvin/tag controls
+ are not green and the disposition is decision. The owner already authorized
+ ordinary work/review/merge in this session. Root's task message accepts the
+ dependency feature scope and this correction; no new user approval is invented.
+ Versions, tags, publication and releases remain excluded.
+6. Accepted: parent baselines were incomplete. V2 retains actual command baselines
+ before any production edit, including their inherited and harness failures.
+ Automatic API runs with a shared compiler target are not counted as isolated
+ proof. Separate current/parent JSON builds succeeded; exact-tag --locked fails
+ on its stale committed lock and remains unmet. This is not masked by a generated
+ lock or a parent API comparison.
+
+Advice adopted: thumb code generation, exact feature variants, separate source and
+package epochs, publication limits, and explicit current/tag API scope. Registry
+NeBu's older Dot code is a risk, not an automatic prediction of failure: the actual
+same four package-H264 controls pass in both debug and release (records 66/67).
+No broader H264 domain equivalence follows from those four controls.
+
+The optional-honeycrisp advice's cache premise was stale: record 56 resolves acpu
+and fails in nox on absent `acpu::field::ntt_forward` and `multilinear_eval` symbols.
+This is now the precise inherited optional-feature boundary. All parent sources and
+locks remain unchanged.
+
+Preparation corrections are visible: records 19–37 invoked Homebrew cargo with
+unsupported `+toolchain` syntax; 38–56 use the rustup shim. Record 46's Clippy mixed
+Homebrew driver with rustup rustc; 57 uses an explicit toolchain-bin PATH and exposes
+the real existing needless_borrow lint. Record 58 similarly pins rustfmt. The
+package-H264 builder initially assumed spaced manifest syntax and stopped before
+writing its manifest; corrected builder uses a new isolated directory. Those are
+harness preparation errors, not production findings. Portable v1 first had two Nu
+parse errors; both are documented with its original verifier retained, and actual
+portable replay passes after correction.
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/README.md b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/README.md
new file mode 100644
index 0000000..991a0b1
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/README.md
@@ -0,0 +1,106 @@
+# Hemera no_std feature boundary
+
+Fresh CODE APPROVE with no blockers; portable Nu replay PASS. This remains a
+source decision with red/unverified gates, not a clean release or registry-delivery
+result. [Final review disposition](review/disposition.md) preserves the full
+verdict and qualifies its unproven performance explanation.
+The two reviewed changes opt Nox out of Hemera defaults and forward Nox's explicit
+`std` feature to `hemera/std`, then add the named real thumb code-generation gate.
+All 48 owning Rust files, dependency paths, versions, optionality and source locks
+remain unchanged. Parent: `0b1407a4b855e4961ede07e1b7ea199cb8018c30`.
+
+Kadek still resolves unchanged registry nox 0.2.0. This upstream source fix does
+not close Kadek's dependency delivery or its separate alloc/math work. No version,
+tag, publication or release action is included. Default-feature opt-out changes
+transitive feature inheritance: Hemera `Hash::to_hex` and `std::io::Read` for
+`OutputReader` require explicit std enablement. Nox does not call them; the named
+consumer manifests independently enable Hemera defaults. This is a manifest/source
+inventory, not successful full consumer or product compilation.
+
+## Reproduce the evidence
+
+From the repository root:
+
+```sh
+nu audit/2026-10-13-hemera-no-std/verify.nu audit/2026-10-13-hemera-no-std
+```
+
+Requirements: Nushell, Git (only `hash-object`), tar/gzip, mktemp and readlink.
+No Cargo, network, sibling checkout, Ruby or Python is needed for this replay.
+Historical Ruby capture/build/verifier programs remain raw evidence inside the
+archive. Do not execute them as a substitute for this portable verifier.
+
+The immutable base is [PLAN v2](../2026-10-13-hemera-no-std-plan-v2/README.md).
+Its archive/index/verifier digests are pinned in [capsule.json](capsule.json).
+This capsule adds 213 content-addressed objects and borrows 303 from that base:
+526494 compressed bytes, 921 logical payloads. Both directories must travel
+together. [index.json](index.json) maps every logical name to exact bytes, SHA-256
+and local/base storage. It includes all 904 CODE support files, full raw streams,
+source archives, the first preparation failures and independent replay receipts.
+There are no loose Cargo manifests for Cargo's Git-package scanner to discover.
+
+The verifier checks the full base, reconstructs the exact 220069-byte CODE input
+`aebaed2fa934763ec3f401c0cb1414b8e6aeae7a93ef9d4c73d3d6d315377e46`, verifies every
+object, all 103 command receipts/206 streams, the 536-entry source bridge with
+exactly two changed files, 52 normalized-package entries and 48 unchanged Rust
+files, actual compiler-root separation, and raw Criterion threshold arithmetic.
+It reconstructs historical inputs and validates recorded outcomes; it does not
+rerun compilation or benchmarks. The original source-freeze verifier separately
+checked the live worktree diff at capture. This portable replay checks that exact
+patch digest and source bodies, without pretending the historical live check is
+performed again.
+
+## Measured gates and remaining boundaries
+
+All commands, cwd, environment, timestamps, runner hashes and streams live at
+logical `code/support/execution/records/<record>/`; [execution notes](../../.claude/tasks/hemera-no-std/execution.md)
+name the exact source epochs. Parent gates precede the production edit. Candidate
+source is the two-file patch
+`387f9ccee4480bbfeb957ee9a2cbb7d959ac808db5635a3f296ee51b001f3899`.
+
+| Gate | Actual result and raw record |
+| --- | --- |
+| Real thumb code generation | Parent sibling38 and normalized-package68 fail `error[E0463]: can't find crate for std` at Hemera; candidate72/96 pass. |
+| Workspace and feature tests | Candidate74/75/76: 161 passing each; parallel77 and brakedown78: 164 each. |
+| Actual H264 controls | Four controls pass in each sibling debug84/release85 and normalized-package debug98/release99 run. These are bounded controls, not the complete codec-domain suite. |
+| Packaging and host | Package95 contains 52 files; package97 passes161 library tests. CLI86/87 and wgpu88 pass; CLI87 has zero tests. Nightly82 passes with zero doctests. |
+| Feature inheritance | Candidate90 has no Hemera/std; explicit std91 and variants92–94 do. |
+| Current-parent API | Explicit JSON comparison101: 229 passing checks, 31 skips. Exact artifacts63/100 came from distinct actual compiler targets. Dependency feature inheritance is outside this tool's model. |
+| Required exact last-tag API | Unmet: exact v0.2.0 locked build64 fails `error: cannot update the lock file`. [Named follow-up](../../.claude/tasks/exact-tag-api-baseline/research.md). Automatic diagnostics60/61 have shared-target ambiguity and do not replace this gate. |
+| fmt | Candidate79 remains red; stdout equals parent58 after only source-prefix normalization. |
+| Clippy | Candidate80 retains parent57 source error: `error: this expression creates a reference which is immediately dereferenced by the compiler`, `cli/main.rs:247:52`. Final Cargo wrapper differs, so full stream equality is not claimed. |
+| Strict docs | Candidate81 retains parent47: `error: unresolved link to 11`. Exact backticks and source context are in raw stderr. |
+| honeycrisp | Candidate89 retains parent56 missing `acpu::field::ntt_forward` and `multilinear_eval`. |
+| Trident/product | Parent59 stops at unavailable cached clap4.5.57. Ring1 product integration remains unverified; static dependency-version findings are not substituted for the observed first error. |
+| Performance | Red/unverified. Initial49/83 breaches 5 of 9 predeclared thresholds; the single planned repeat102/103 breaches 6 of 9. Cause is unestablished. |
+
+For repeat102/103, median changes are particle +43.12%, tree +89.64%, pattern hash
++5.28%, hash chain +46.90%, inverse +21.08%, look +15.82%; add and multiply reverse
+direction from the initial pair. Raw samples/estimates and both comparisons remain
+in logical `code/support/execution/benchmark/`. Root paused heavy Cargo work for
+the repeat; this agent compiled nothing concurrently. Other system load/frequency
+was not measured. Equal 3028144-byte executable sizes but unequal file hashes do
+not prove code equality, noise, a regression cause or a performance improvement.
+No extra repetitions or source tuning were hidden.
+
+## Review lineage and preparation failures
+
+PLAN v1 was rejected. Its full input, raw verdict and disposition remain in the
+[original capsule](../2026-10-13-hemera-no-std-plan/README.md) and immutable PLAN v2
+support. Fresh Opus PLAN v2 approved the exact input at
+`2026-10-13T02:23:59.183394Z`; [raw approval](review/plan-v2/stdout.json),
+[invocation](review/plan-v2/invocation.json), [completion](review/plan-v2/completion.json).
+CODE v1 was independently reconstructed by root before a fresh vendor review.
+The capsule's frozen pending-review statement is historical; the later actual
+CODE APPROVE is bound by the separate [outer disposition](review/disposition.md).
+
+Records19–37 are failed Homebrew `+toolchain` dispatch, not source compilation;
+record46 is mixed Clippy-driver/toolchain failure, superseded by pinned-driver57.
+The first freeze helper compared UTF-8 and binary Ruby strings incorrectly even
+though their digests matched; the corrected binary comparison passed without a
+source change. The first execution verifier omitted `nu --stdin`; its preserved
+body and failure are evidence, not a gate failure. All corrected actual outcomes
+are bound to their own receipts; none overwrites an earlier epoch.
+
+Portable verifier preparation failures and the successful later replay are
+retained separately in [verification preparation](verification/preparation.md).
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/capsule.json b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/capsule.json
new file mode 100644
index 0000000..bbe4437
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/capsule.json
@@ -0,0 +1,26 @@
+{
+ "parent": "0b1407a4b855e4961ede07e1b7ea199cb8018c30",
+ "review_bytes": 220069,
+ "review_sha256": "aebaed2fa934763ec3f401c0cb1414b8e6aeae7a93ef9d4c73d3d6d315377e46",
+ "sections": 50,
+ "support_files": 904,
+ "records": 103,
+ "production_files": 2,
+ "performance_gate": "red/unverified",
+ "required_exact_tag_gate": "unmet",
+ "source_patch_sha256": "387f9ccee4480bbfeb957ee9a2cbb7d959ac808db5635a3f296ee51b001f3899",
+ "archive_sha256": "b3ce8ef34ef80b59d0dd4a5c979490faffe009fbcdf4795805aabfcbd9219ed9",
+ "archive_bytes": 526494,
+ "index_sha256": "b83bc1ca01d1c0ac1d7f7af2b5b7c9a120c11c01584dd08f562c74852b14de4d",
+ "logical_payloads": 921,
+ "unique_objects": 516,
+ "new_objects": 213,
+ "borrowed_objects": 303,
+ "base": {
+ "relative_path": "../2026-10-13-hemera-no-std-plan-v2",
+ "archive_sha256": "02a61c325f3c72834dbe3c92674ebc20828fd17b4d35f3a7b7ae1ddc41f6ffca",
+ "index_sha256": "506c29bf7af4b15d55155d86e95e86b63b7a23c9b8789f726305f4fb47fadfa2",
+ "verifier_sha256": "d8dee4b5cab26947264ec31b0397d6efb857baeb7734a0a0e28e9ed18046adc1"
+ },
+ "state_at_freeze": "PLAN v2 APPROVE; exact candidate tested; CODE v1 independently replayed and fresh Opus CODE pending. Source frozen. Performance red/unverified, inherited named gate failures and exact last-tag locked API unmet; ordinary source decision only, no release or registry publication."
+}
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/evidence.tar.gz b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/evidence.tar.gz
new file mode 100644
index 0000000..2c3a589
Binary files /dev/null and b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/evidence.tar.gz differ
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/files.json b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/files.json
new file mode 100644
index 0000000..46b7263
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/files.json
@@ -0,0 +1,202 @@
+[
+ {
+ "file": "README.md",
+ "bytes": 7670,
+ "sha256": "837b33c221639a5f9b714e2a7c902f929c1f41aade01e6f9af811c06a5c74c4d"
+ },
+ {
+ "file": "capsule.json",
+ "bytes": 1377,
+ "sha256": "9a83cac4b65a60d7151975a37171e0b21c90b5a6a8652e1e20068615b86abfc3"
+ },
+ {
+ "file": "evidence.tar.gz",
+ "bytes": 526494,
+ "sha256": "b3ce8ef34ef80b59d0dd4a5c979490faffe009fbcdf4795805aabfcbd9219ed9"
+ },
+ {
+ "file": "index.json",
+ "bytes": 192396,
+ "sha256": "b83bc1ca01d1c0ac1d7f7af2b5b7c9a120c11c01584dd08f562c74852b14de4d"
+ },
+ {
+ "file": "review/code-v1/benchmark-statistic-check.json",
+ "bytes": 1448,
+ "sha256": "901ff2d2c92102f6814a66d23c1233ced389db98ed4f271cbedf4610fe375f07"
+ },
+ {
+ "file": "review/code-v1/completion.json",
+ "bytes": 240,
+ "sha256": "066e3be88e78201e711410659867ac4555d55cea064b64289f18d0e28adec5e0"
+ },
+ {
+ "file": "review/code-v1/invocation.json",
+ "bytes": 1202,
+ "sha256": "957ca06361086251e1665c46b99fa4c7014090bd7e7c52daf1fd06660c23cd59"
+ },
+ {
+ "file": "review/code-v1/launcher.rb.txt",
+ "bytes": 1736,
+ "sha256": "a60044a087e3b792a9a4c0413bb5eed258ae6ac7201c1c3a752a81306a608fa3"
+ },
+ {
+ "file": "review/code-v1/stderr.txt",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "review/code-v1/stdout.json",
+ "bytes": 14962,
+ "sha256": "e1d6a706192fd767cab1756824f6cbb6a0805b7e16664b3263d6aaf099284b6c"
+ },
+ {
+ "file": "review/code-v1/verdict.md",
+ "bytes": 12881,
+ "sha256": "2142ea0cdc0b054fa50fc8a7d411da4d492c1804611777d616148019a49c497c"
+ },
+ {
+ "file": "review/disposition.md",
+ "bytes": 2818,
+ "sha256": "7e7659dd9fc8732d4dbd860701010c130e9fcb62750d04558b8652c6bad824cf"
+ },
+ {
+ "file": "review/plan-v2/completion.json",
+ "bytes": 240,
+ "sha256": "ff0f11c5ee1be4eadcc56c520fc90dc6bca3159ffa3d9405a449db4bd3a016f9"
+ },
+ {
+ "file": "review/plan-v2/invocation.json",
+ "bytes": 1202,
+ "sha256": "fbe84fa12aebb34017f6938a8a5bcb3b2a534f09543125f86abb4b1908c276ef"
+ },
+ {
+ "file": "review/plan-v2/stderr.txt",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "review/plan-v2/stdout.json",
+ "bytes": 12273,
+ "sha256": "1bd21c68c348163df8bd58a0205772732e50dfc733d30374aa61cdf88d09c223"
+ },
+ {
+ "file": "verification/capture.rb.txt",
+ "bytes": 872,
+ "sha256": "10fc0f8210a06cd42e2cc85d0f2b328da05a5e09e01c8feb75651b31fdb0d5d6"
+ },
+ {
+ "file": "verification/final-checks.json",
+ "bytes": 4569,
+ "sha256": "896da84ffa8447d54153fbde45e76e99d46b1f66de3cbd55fe2885ef329cb581"
+ },
+ {
+ "file": "verification/final-checks.rb.txt",
+ "bytes": 2816,
+ "sha256": "6ff10415c0f52a6be9a8f458582d72ba41e0a7e69e9ffd89fe8ee2000a01f70b"
+ },
+ {
+ "file": "verification/portable-final-inputs.json",
+ "bytes": 779,
+ "sha256": "3a6aba7e140b1c84e5f8b9d50d158d8889c03563cf51e02a4208d6ceaab43331"
+ },
+ {
+ "file": "verification/portable-final.json",
+ "bytes": 778,
+ "sha256": "bb606045073b4000aee6191d747a673b09aab0f0a22dd8cb64654f7f774f9bfc"
+ },
+ {
+ "file": "verification/portable-final.stderr",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "verification/portable-final.stdout",
+ "bytes": 1360,
+ "sha256": "61f79c264c4bc424685a4e8bd0f6e46a49dbca1cd098d59e1d048a07de9c0544"
+ },
+ {
+ "file": "verification/portable-v1.json",
+ "bytes": 771,
+ "sha256": "f42cf00e98441fd76453f33d609f1f9410c0d3ebd59220a5bbcb3c79e2f7a3c2"
+ },
+ {
+ "file": "verification/portable-v1.stderr",
+ "bytes": 294,
+ "sha256": "5eff472aa6d34b964607bb10fea30bf04509ce4a2d7e44e8d8dc10292f960fdb"
+ },
+ {
+ "file": "verification/portable-v1.stdout",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "verification/portable-v2.json",
+ "bytes": 771,
+ "sha256": "ba2a6aab027e72fc97a4251b4d6ccf915ccfea678cd072c1ca6d3f9f52ed207f"
+ },
+ {
+ "file": "verification/portable-v2.stderr",
+ "bytes": 793,
+ "sha256": "548656c99158a1639fd41008f2b8b4d70482b039afa0c3390f43f9dd3e7454f4"
+ },
+ {
+ "file": "verification/portable-v2.stdout",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "verification/portable-v3.json",
+ "bytes": 771,
+ "sha256": "841b51061c9a09ad631e9b284ba028b978a70b6cd6d7821c4096f74742c76662"
+ },
+ {
+ "file": "verification/portable-v3.stderr",
+ "bytes": 942,
+ "sha256": "a36f3a09f5ad60bfaceed3079606ba7b1e645b059d55ecae3a6b75b5303f35fc"
+ },
+ {
+ "file": "verification/portable-v3.stdout",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "verification/portable-v4.json",
+ "bytes": 772,
+ "sha256": "eb61c82d6faad6570ef45d659131db3fbedd420277e7380fc4504c0a12587720"
+ },
+ {
+ "file": "verification/portable-v4.stderr",
+ "bytes": 0,
+ "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
+ },
+ {
+ "file": "verification/portable-v4.stdout",
+ "bytes": 1360,
+ "sha256": "61f79c264c4bc424685a4e8bd0f6e46a49dbca1cd098d59e1d048a07de9c0544"
+ },
+ {
+ "file": "verification/preparation.md",
+ "bytes": 1089,
+ "sha256": "13a7e708d1e82edf8864236bf1df41c8a8ff4b7bd667ca893098456d5843ea4c"
+ },
+ {
+ "file": "verification/verify-diagnostic.nu.txt",
+ "bytes": 20050,
+ "sha256": "a2e60f627dc6ea4b3158f720fce2feff7a0b8ad88d0a1c866266e2953a126ddb"
+ },
+ {
+ "file": "verification/verify-first.nu.txt",
+ "bytes": 20012,
+ "sha256": "49439bd83162089d762e2e131c3067aa96a4be1e62302f6865f9ae27fc80630d"
+ },
+ {
+ "file": "verification/verify-third.nu.txt",
+ "bytes": 20052,
+ "sha256": "3b721205fece2eed1c095f72b63d170c995bc944087a537a90e1e987bd4a19e2"
+ },
+ {
+ "file": "verify.nu",
+ "bytes": 21538,
+ "sha256": "95e2b0ca65a253cb9332def60bcc4bdd21489db6367b4e9a756748e8a187c1cc"
+ }
+]
diff --git a/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/index.json b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/index.json
new file mode 100644
index 0000000..fe68a8d
--- /dev/null
+++ b/Users/master/.cache/cyber/nox/hemera-feature-performance/cells/D/nox/audit/2026-10-13-hemera-no-std/index.json
@@ -0,0 +1,5528 @@
+[
+ {
+ "path": "code/manifest.json",
+ "bytes": 428,
+ "sha256": "6ba346eef8f03ba3c8fdf3bbc2c0e9a8153592c5bf2e8748b6333aa588a7356c",
+ "storage": "local"
+ },
+ {
+ "path": "code/omissions.json",
+ "bytes": 164148,
+ "sha256": "011c019e854ced906502bc0b157ebc3ffe070c673959c0ab1dc9fc302faf7e91",
+ "storage": "local"
+ },
+ {
+ "path": "code/parts/012.txt",
+ "bytes": 1130,
+ "sha256": "8fa241bf5af557ef0ff69a88d180082d4d64debeaa7e6fdcde19a9ea0b94e6f1",
+ "storage": "base"
+ },
+ {
+ "path": "code/parts/013.txt",
+ "bytes": 3281,
+ "sha256": "450a34b6ede9e9e890ac4dd78d81b616dd9ffd7e226e8bd2d5b22b3477f5110d",
+ "storage": "base"
+ },
+ {
+ "path": "code/parts/014.txt",
+ "bytes": 1799,
+ "sha256": "ed08ddcf753ea07a95cca537306c3f56af5a001a1736617bf9ff1f450317772f",
+ "storage": "base"
+ },
+ {
+ "path": "code/parts/020.txt",
+ "bytes": 6023,
+ "sha256": "3545bb77998920d6f7c4a03eecf13861151c360449b244d3267e51dd4edc01f9",
+ "storage": "base"
+ },
+ {
+ "path": "code/parts/043.txt",
+ "bytes": 396,
+ "sha256": "b3fbbfbef4f7744bd8d1deb0442bcabd96f8ec9043ffb3aa920f4d0e285c92f6",
+ "storage": "local"
+ },
+ {
+ "path": "code/parts/049.txt",
+ "bytes": 401,
+ "sha256": "54e5b095addfa418a3e2cbf6b6fc16f7787ecea7a00c85ccad0277a982e38c8c",
+ "storage": "local"
+ },
+ {
+ "path": "code/review.txt",
+ "bytes": 220069,
+ "sha256": "aebaed2fa934763ec3f401c0cb1414b8e6aeae7a93ef9d4c73d3d6d315377e46",
+ "storage": "local"
+ },
+ {
+ "path": "code/sections.json",
+ "bytes": 13308,
+ "sha256": "33443516c587d60c4edf10d7dcd305f9332d5eef868f6355f5ba12cf55dbdfc5",
+ "storage": "local"
+ },
+ {
+ "path": "code/support-index.json",
+