aura graph: blueprint view panics (unimplemented!) on nested composites #26

New Issue

2026-06-05T21:00:09+02:00

Brummel commented

2026-06-05 21:00:09 +02:00

Cycle 0013 (#13) shipped the aura graph ASCII-DAG render with two views. The blueprint (clustered) view in crates/aura-cli/src/graph.rs hits unimplemented!("nested-composite cluster rendering is a follow-up") (graph.rs ~line 74) when a composite contains another composite as an interior item.

Capability divergence between the two views: Blueprint::compile() and the --compiled (flat) render handle arbitrary nesting fine, but the clustered blueprint view does not — a nested-composite blueprint renders flat but panics clustered. The built-in sample is single-level, so nothing reachable today triggers it; it goes live as soon as aura graph renders an arbitrary nested blueprint.

Direction: render nested composites as nested ascii-dag subgraphs (clusters within clusters), or minimally flatten an interior composite into its parent cluster; resolve the producer_id/consumer_ids boundary resolution recursively.

Related low-severity render gap in the same file (graph.rs ~line 99): source nodes are labelled source:{kind} because SourceSpec carries no name — two F64 sources render indistinguishably. A SourceSpec name field (non-load-bearing, like Composite.name) would fix it; latent C20 gap.

context: known limitation deferred by cycle 0013; the built-in sample does not exercise it.

Cycle 0013 (#13) shipped the `aura graph` ASCII-DAG render with two views. The blueprint (clustered) view in crates/aura-cli/src/graph.rs hits unimplemented!("nested-composite cluster rendering is a follow-up") (graph.rs ~line 74) when a composite contains another composite as an interior item. Capability divergence between the two views: Blueprint::compile() and the --compiled (flat) render handle arbitrary nesting fine, but the clustered blueprint view does not — a nested-composite blueprint renders flat but panics clustered. The built-in sample is single-level, so nothing reachable today triggers it; it goes live as soon as aura graph renders an arbitrary nested blueprint. Direction: render nested composites as nested ascii-dag subgraphs (clusters within clusters), or minimally flatten an interior composite into its parent cluster; resolve the producer_id/consumer_ids boundary resolution recursively. Related low-severity render gap in the same file (graph.rs ~line 99): source nodes are labelled source:{kind} because SourceSpec carries no name — two F64 sources render indistinguishably. A SourceSpec name field (non-load-bearing, like Composite.name) would fix it; latent C20 gap. context: known limitation deferred by cycle 0013; the built-in sample does not exercise it.

Brummel added the feature label 2026-06-05 21:00:09 +02:00

Brummel referenced this issue

2026-06-05 22:36:08 +02:00

aura graph / render: expose rendering for a consumer's OWN graph (not just the built-in sample) #28

Brummel referenced this issue from a commit

2026-06-05 23:01:24 +02:00

audit: cycle 0013 tidy (carry-on, debt filed)

Brummel closed this issue

2026-06-05 23:01:24 +02:00

Brummel referenced this issue from a commit

2026-06-05 23:01:24 +02:00

fieldtest: milestone construction-layer — 4 examples, 7 findings