Named fold subscription's data-authorability boundary — data selector vs Rust-only
Cycle close (2026-07-24)
Shipped on branch worktree-issue-310-fold-data-authorability (merge = owner): 1baee77 (feature: --tap TAP=FOLD selector on aura run, C27 Current-state…
C14 exit-class evidence from the #310 cycle audit (2026-07-24)
The #310 architect review flagged: tap-bind refusals reached from argv content exit through the assembly crate's runner-side…
measure ic is reachable from the release binary
Prerequisite surfaced by the #310 skeptic pass (2026-07-24)
Two disjoint tap namespaces exist and this milestone is where they meet: the presentation channel (Presentation.persist_taps over…
Named fold subscription's data-authorability boundary — data selector vs Rust-only
Design reconciliation (specify, /boss 2026-07-24)
Spec: fold-subscription-data-selector (cycle in progress). The fork below is still listed open on this issue; this records its derived…
Triage (2026-07-24)
Milestone container created for the ratified retirement (this issue + #328). Sequence: #328 first — the binary-only M1 fieldtest showed the sugar and document axis…
graph.<node>.<param> vs document <node>.<param> (open-only)
Triage (2026-07-24)
Sorted into the new Sugar retirement milestone as its first item: the ratified #319 retirement makes the document form the only sweep-axis surface, so this…
sweep --trace never persists a declared tap despite the op doc calling it recordable
Triage (2026-07-24)
Sorted into the Measurement reachable milestone: this bug is the missing mechanism for #312 (see the fieldtest evidence comment there), so the milestone-internal…
Empirical confirmation — binary-only M1 milestone fieldtest (2026-07-24)
The check announced above ran: a fieldtest agent bootstrapped from the release binary (d26f0c8) alone — no sources,…
Additional case from the binary-only M1 milestone fieldtest (2026-07-24)
Plain aura run on the synthetic stream: 18 cycles → 0 trades → all-zero metrics, with no notice that the built-in…
measure ic is reachable from the release binary
Fieldtest evidence (binary-only M1 milestone fieldtest, 2026-07-24)
The dead-end is confirmed end-to-end from the release binary (d26f0c8): the only persistable taps are the presentation set…
graph
--vocabulary one-liner — give each a charge-basis-specific meaning
campaign introspect describes process.ref as a bare content id; the validator requires the tagged `{content_id}
graph.<node>.<param> vs document <node>.<param> (open-only)
sweep --trace never persists a declared tap despite the op doc calling it recordable