Ratify or fix: an exec --override single run mints a different, unstored topology_hash #343

New Issue

2026-07-26T00:22:20+02:00

claude commented

2026-07-26 00:22:20 +02:00

Spec-gap finding from the M42 milestone fieldtest (2026-07-26, corpus fieldtests/milestone-42-sugar-retirement/).

aura exec <bp> --override <path>=<value> reopens the named bound knob before bootstrap, so the executed signal's canonical bytes — and therefore the manifest's topology_hash — differ from the same blueprint executed without the flag, even when the override re-binds the param to its existing bound value (a no-op override). The minted hash corresponds to a blueprint variant that exists nowhere in the store, so topology_hash no longer resolves to a registered artifact for overridden runs.

The campaign leg has the same property through the ratified #246 axis-over-bound-param path (a reopened member's hash has always been the reopened topology's), so this may simply be the mechanism working as designed and want ratification prose in C12/C18/C24 (an override IS a topology-parameter variation; the manifest's params map plus the base document reconstruct it). Alternatively the single-run leg could stamp the base blueprint's stored hash plus the override record. Decide and ratify one reading; today the behaviour is accidental-undocumented.

depends on: C12/C18 identity prose (the reproduction-identity clause)
context: surfaced by the #319 retirement's new --override residue; no observed misbehaviour beyond the unstored id.

Spec-gap finding from the M42 milestone fieldtest (2026-07-26, corpus `fieldtests/milestone-42-sugar-retirement/`). `aura exec <bp> --override <path>=<value>` reopens the named bound knob before bootstrap, so the executed signal's canonical bytes — and therefore the manifest's `topology_hash` — differ from the same blueprint executed without the flag, even when the override re-binds the param to its existing bound value (a no-op override). The minted hash corresponds to a blueprint variant that exists nowhere in the store, so `topology_hash` no longer resolves to a registered artifact for overridden runs. The campaign leg has the same property through the ratified #246 axis-over-bound-param path (a reopened member's hash has always been the reopened topology's), so this may simply be the mechanism working as designed and want ratification prose in C12/C18/C24 (an override IS a topology-parameter variation; the manifest's params map plus the base document reconstruct it). Alternatively the single-run leg could stamp the base blueprint's stored hash plus the override record. Decide and ratify one reading; today the behaviour is accidental-undocumented. depends on: C12/C18 identity prose (the reproduction-identity clause) context: surfaced by the #319 retirement's new `--override` residue; no observed misbehaviour beyond the unstored id.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Brummel/Aura#343