Blueprint-store on-ramp: register a blueprint file, file-level content id, param-space listing #196
Reference in New Issue
Block a user
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?
A campaign's strategy ref cannot be driven to resolve from the public surface (fieldtest cycle-0106, F5): (a) no verb computes a blueprint FILE's content id — graph introspect --content-id consumes an op-list, not a blueprint JSON; (b) no verb registers a standalone blueprint into runs/blueprints/ (only sweep/mc/walkforward populate it as a side effect); (c) no verb lists a strategy's param_space, so the axis names/kinds a campaign needs are undiscoverable without running a sweep first — which is what the campaign describes.
Likely shape (scoped with the executor cycle): 'aura graph register <blueprint.json>' (store put keyed by content id), a blueprint-file mode for --content-id, and a param-space listing verb (names + ScalarKinds) so campaign axes can be authored against a strategy handle.