Brummel/Aura
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases Wiki Activity

aura-engine should re-export the core scalar vocabulary (ScalarKind etc.) a graph-builder needs #29

New Issue
Closed
opened 2026-06-05 22:36:08 +02:00 by Brummel · 0 comments
Brummel commented 2026-06-05 22:36:08 +02:00
Owner
Copy Link
Copy Source

Milestone fieldtest friction (Construction layer): a consumer building a Blueprint against aura-engine must reach for ScalarKind / Firing / Scalar to declare SourceSpec kinds and Recorder columns, but aura-engine re-exports only the wiring types (Blueprint, BlueprintNode, Composite, OutPort, Edge, Target, SourceSpec, Harness, ...). The consumer hits a compile error and must add a separate aura-core dependency + import path to get ScalarKind.

A paper cut, not a blocker — the compiler names the missing symbol — but the construction surface (aura-engine) ought to re-export the scalar vocabulary its own public types (SourceSpec.kind, etc.) require, so a graph-builder needs one crate, not two.

Direction: pub use aura_core::{Scalar, ScalarKind, Firing, Timestamp} (or the relevant subset) from aura-engine.

context: surfaced by the Construction-layer milestone fieldtest; pure ergonomics tidy.

Milestone fieldtest friction (Construction layer): a consumer building a Blueprint against aura-engine must reach for ScalarKind / Firing / Scalar to declare SourceSpec kinds and Recorder columns, but aura-engine re-exports only the wiring types (Blueprint, BlueprintNode, Composite, OutPort, Edge, Target, SourceSpec, Harness, ...). The consumer hits a compile error and must add a separate `aura-core` dependency + import path to get ScalarKind. A paper cut, not a blocker — the compiler names the missing symbol — but the construction surface (aura-engine) ought to re-export the scalar vocabulary its own public types (SourceSpec.kind, etc.) require, so a graph-builder needs one crate, not two. Direction: `pub use aura_core::{Scalar, ScalarKind, Firing, Timestamp}` (or the relevant subset) from aura-engine. context: surfaced by the Construction-layer milestone fieldtest; pure ergonomics tidy.
Brummel added the idea label 2026-06-05 22:36:08 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
BLOCKER
Core functionality blocked; preempts other selection
 bug
Observable misbehaviour
 feature
Substantial extension; no full spec required
 idea
Droppable; no commitment
No Label idea
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude (Claude) Brummel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Brummel/Aura#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?