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

Blueprint on-ramp: graph register / --params reject the op-script form; the graph build bridge is invisible #202

New Issue
Closed
opened 2026-07-03 22:28:20 +02:00 by Brummel · 0 comments
Brummel commented 2026-07-03 22:28:20 +02:00
Owner
Copy Link
Copy Source

Fieldtest cycle-0107 F5 (fieldtests/cycle-0107-campaign-executor/FINDINGS.md): the corpus's canonical strategy form is an op-script, and 'aura graph introspect --content-id FILE' shape-discriminates it — but 'aura graph register FILE' and 'aura graph introspect --params FILE' reject it with a raw serde message ('invalid type: map, expected u32') that never names the 'aura graph build' bridge. The three on-ramp verbs disagree on accepted shapes. Fix: shape-discriminate the op-list in register/--params as --content-id already does (content id is shape-invariant — op-script and its built envelope hash identically, verified), or make the refusal name the bridge. Repro: aura graph register fieldtests/cycle-0107-campaign-executor/c0107_1_smacross_open.json

Fieldtest cycle-0107 F5 (fieldtests/cycle-0107-campaign-executor/FINDINGS.md): the corpus's canonical strategy form is an op-script, and 'aura graph introspect --content-id FILE' shape-discriminates it — but 'aura graph register FILE' and 'aura graph introspect --params FILE' reject it with a raw serde message ('invalid type: map, expected u32') that never names the 'aura graph build' bridge. The three on-ramp verbs disagree on accepted shapes. Fix: shape-discriminate the op-list in register/--params as --content-id already does (content id is shape-invariant — op-script and its built envelope hash identically, verified), or make the refusal name the bridge. Repro: aura graph register fieldtests/cycle-0107-campaign-executor/c0107_1_smacross_open.json
Brummel added the feature label 2026-07-03 22:28:20 +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 feature
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#202
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?