Document SessionFrankfurt/Session output semantics (+ a worked declared-tap authoring example) #285
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?
Surfaced by the measurement-milestone fieldtest. SessionFrankfurt semantics are undocumented on the public surface: a blueprint author reaching for session anchoring (the milestone acceptance sketch turns on it) has no ledger/glossary/README statement of what SessionFrankfurt emits (the bars_since_open index, its open reference, the timezone/DST handling, the isfirst==0 boundary) beyond reading the node source. The fieldtester had to infer it. This is a docwriter/glossary follow-up: document SessionFrankfurt (and its sibling Session) output semantics so a downstream author can wire session-anchored studies from the public interface alone. Also folds in: C27 declared taps are recorded in the design ledger but not yet in user-facing docs/README/glossary examples (the glossary tap entry was updated to record the second sense this cycle; a worked authoring example is still owed at the next docwriter window).