Files
Brummel 7e195f66b7 fieldtest: milestone construction-layer — 4 examples, 7 findings
End-to-end milestone fieldtest (closing gate) for the "Construction layer"
milestone (#12 composites + #13 aura graph render). Four real downstream tasks
authored against the PUBLIC interface only (ledger + doc-comments + re-exports
+ the aura CLI), under fieldtests/milestone-construction-layer/:
  mc_1 — author a named sma_cross composite, build a Blueprint, compile +
         bootstrap + run (12 populated equity rows);
  mc_2 — correct vs fast/slow-swapped cross: labels + graph-as-data differ
         observably (the headline mis-wire-visible property);
  mc_3 — composite-nested-in-composite inlines and runs;
  mc_4 — walk the built graph via the read-only accessors, no engine internals.

Roll-up: friction_found, NO bugs. The milestone delivers its core promise —
fractal authoring -> compile -> bootstrap -> run, introspection as graph-as-data,
and param-carrying labels that make a mis-wire readable. None of the findings
block the gate.

Findings filed to the forward queue (not fixed here):
- #28 (feature) — the headline friction: `aura graph` renders only the built-in
  sample and the render adapter is CLI-private, so a consumer can't render their
  OWN graph. Subsumes the reachability of #26 (the nested-render panic is
  structurally unreachable until the render is parameterizable). Likely next
  (consumer-project / World) milestone.
- #29 (idea) — aura-engine doesn't re-export the scalar vocabulary (ScalarKind
  etc.) a graph-builder needs; one-crate ergonomics tidy.
- #16 (comment) — `aura graph` arg policy (help / unknown-arg) should unify with
  the still-open `aura run` strictness question.

The fieldtester read no implementation source; all artefacts are the consumer
crate + the two live render captures (render_clustered.txt / render_compiled.txt,
byte-identical across runs).
2026-06-05 22:38:39 +02:00

40 lines
1.1 KiB
TOML

# Milestone fieldtest consumer crate — Construction layer.
#
# A standalone downstream project (the shape a C16 research project takes):
# path-deps on the engine crates only. It drives the construction layer
# (Blueprint / Composite / compile / bootstrap / run) and the graph-as-data
# accessors from the PUBLIC interface only — no crates/*/src was read; the
# API was discovered from the design ledger (docs/design/INDEX.md) + rustdoc
# doc-comments + the public re-exports.
#
# Empty [workspace] table: this fixture crate is its OWN workspace root, so it
# is not pulled into the aura engine workspace.
[workspace]
[package]
name = "ms-construction-layer-fieldtest"
edition = "2024"
version = "0.0.0"
publish = false
[[bin]]
name = "composite_build_run"
path = "mc_1_composite_build_run.rs"
[[bin]]
name = "miswire_render"
path = "mc_2_miswire_render.rs"
[[bin]]
name = "nested_composite"
path = "mc_3_nested_composite.rs"
[[bin]]
name = "introspect_graph"
path = "mc_4_introspect_graph.rs"
[dependencies]
aura-core = { path = "../../crates/aura-core" }
aura-std = { path = "../../crates/aura-std" }
aura-engine = { path = "../../crates/aura-engine" }