A tally store is stamped with the buckets, not the clock - #175
Merged
Conversation
A chunk's window is now the min/max of the bucket stamps in it, so both of a tally store's clocks are the minutes its lines are about and `--from`/`--to` selects its chunks exactly. It stamped the moment of computation before, which put the two axes a bucket and a grace apart. That gap was what `logline_lag` existed to bridge, and it goes with it: the manifest key, its parse-check, the widening that consulted it, the derivation on every provisioned store, and the prose. `WIDEN_MS` is the minute of widening it always was, unchanged for every store on disk. The knob was not worth having. Set too low it selects no chunk and answers nothing, which reads exactly like a quiet minute; set wide enough for a backfill it prunes nothing and every query is a full scan. Its one reliable value was the one tally derived, and tally no longer needs it. The remaining case — an arrival-stamped store whose lines carry earlier stamps — is the ROADMAP's zone-map sidecar, which answers it exactly. ⚠ `timberfs tally | timberfs append` is stamped on arrival, as any pipe is, so a logline window over that store finds nothing. Documented where that pipeline is shown; the VM test asserts the window over a store a PROVISIONING wrote, which is the path that has to work.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drops
logline_lagbefore it ships, and removes the reason it existed.The stamping
Sink::writestampednow_ms. A chunk's window is now the min/max of thebucket stamps in it (
append_windowed), so both of a tally store's clocks arethe minutes its lines are about, and
--from/--toselects its chunks exactly.A backfill of last month lands in chunks stamped last month, where selection
prunes.
The rule the receive intakes already follow —
ROADMAP.md:441, "both intakesstamp chunks with the sender's EVENT time". Stamping the moment of
computation was the odd one out.
The recorded justification was stale.
docs/plans/tally.mdsaid the gap made "arevision written an hour late findable on the first" — revisions were replaced by
displacement, so nothing arrives late any more and the gap carried no
information. Nothing read it: cursors hold the chunk
seq, not a time(
format.rs:139), and duplicate buckets are combined by the field's own rule(
timbergraph.py:264), not by arrival order.The knob
Gone entirely — the manifest key, its parse-check, the widening that consulted
it, the derivation on every provisioned store, the
infoline and the prose.WIDEN_MSis the minute of widening it always was, unchanged for every storeon disk.
Set too low it selects no chunk and answers nothing, which reads exactly like a
quiet minute; set wide enough for a backfill it prunes nothing and every query
is a full scan. Its one reliable value was the one tally derived, and tally no
longer needs it. The case that remains — an arrival-stamped store whose lines
carry earlier stamps — is
ROADMAP.md:16's zone-map sidecar, which answers itexactly and cannot be set wrong.
One consequence, documented
timberfs tally | timberfs append --into Xis stamped on arrival, as any pipeis, so a logline window over that store finds nothing. That is
append'smeaning, not tally's. Noted where the pipeline is shown in
deployment.mdandin
timberfs(1).Tests
what_is_written_reports_the_minutes_it_is_aboutpins the window the writepath stamps with, including the
!metaline's stamp.appendpipelineto
tally_provisioning_end_to_end, where it now runs with nothingdeclared: the source lines are dated 2026-09-06 and the run is today, so a
store stamped at computation time would fail it.
Net −82 lines.