Files
Aura/crates/aura-measurement/Cargo.toml
T
claude 5006766579 audit: shell-boundary cycle close — drift resolved in-commit
Cycle-close audit (architect: drift_found; design core clean). What
holds, architect-confirmed with the guard run and the diff read in
full: the shell boundary is real and enforced (full-workspace
c28_layering incl. completeness + shell-content checks, acceptance
grep clean — no member-run symbol left under crates/aura-cli/src);
aura-campaign keeps zero production dependency on the runner; the IC
move is verbatim against the anchor; the new library-only E2E pins C1
(two independent runners, byte-identical RunReport).

Drift items, all resolved as fixes in this commit:
- design ledger: the C28 status sentence "No crate exists yet for
  measurement" contradicted this cycle's own phase-3 done line — now
  records aura-measurement as seeded (#295), execution still unbuilt.
- the #147 registry-dispatch acceptance tests (IC deflation null,
  seeded determinism, cross-vocabulary refusal) were pure library
  properties stranded in the shell's test module — relocated to
  aura-measurement/tests/registry_dispatch.rs (engine/registry as
  dev-only, layering-exempt edges), per the cycle's own tests-move-
  with-their-module rule.
- aura-runner's direct production edge on the external data-server
  tree was structurally invisible (the direction table checks aura-*
  keys only) and unrecorded — the C28 assembly prose now names it, and
  a new c28_layering test pins the external tree's entry points to
  exactly {aura-ingest, aura-runner, aura-cli}.
- the C28 shell prose named three buckets that did not cover two real
  shell residents — it now names the op-script construction front-end
  (translation) and the `aura new` scaffolder (authoring-tooling,
  shell-resident like rendering until a second consumer wants it).

Deliberately deferred, tracker homes exist (not drift): #297
(process::exit sites in aura-runner's single-run verb paths), #294
(IC duplicate-timestamp semantics), #288-era rustdoc unresolved-link
warnings in aura-std/aura-backtest (pre-existing byte-identically at
the anchor).

No regression scripts are configured (the bench is report-only); the
architect review is the gate. Verification: cargo test --workspace
green (1474 passed, 0 failed) incl. the relocated registry-dispatch
tests and the new data-server guard; clippy --workspace --all-targets
-D warnings clean.

refs #295
2026-07-21 06:46:13 +02:00

26 lines
1.0 KiB
TOML

[package]
name = "aura-measurement"
edition.workspace = true
version.workspace = true
license.workspace = true
publish.workspace = true
# C28 rung 3 (measurement): descriptive statistics over market streams.
# Seeded by #295 with the IC. Depends only inward: the scalar vocabulary
# and the domain-free statistics foundation.
[dependencies]
aura-core = { path = "../aura-core" }
aura-analysis = { path = "../aura-analysis" }
# serde (de)serializes IcMetrics for the run registry (C18), mirroring the
# R-vocabulary metric types (aura-backtest, aura-engine); the aligned pairs
# ride #[serde(skip)] (in-memory null inputs only, never persisted).
serde = { workspace = true }
# The #147 registry-dispatch acceptance tests (tests/registry_dispatch.rs)
# exercise the generic deflation machinery over the IC vocabulary — pure
# library properties relocated from the shell with #295. Dev-only edges,
# C28-layering-exempt.
[dev-dependencies]
aura-engine = { path = "../aura-engine" }
aura-registry = { path = "../aura-registry" }