Verify epoch boundaries
Owner role · Data owner
Evidence: The reset and both boundary values are recorded without a missing interval.
Reporting decisions / Delivery leads and report reviewers
Drafting workbenchA completion counter that resets inside a period
Reconstruct a period count from known counter epochs instead of subtracting endpoints across a reset.
A cumulative counter reset is an observation boundary; the kit is not a query recipe or a claim that TeamBoost exposes Prometheus metrics.
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
Prepare a brief for human review
Drafting workbenchSynthetic case: The known counter is 10 at period start, 13 just before a zero reset, 0 after the reset and 4 at period end. Both epochs are complete in the invented log.
Calculate within epochs
Owner role · Reviewer
Evidence: 13−10=3 and 4−0=4 are separate within-epoch changes.
Label reconstruction limits
Owner role · Report owner
Evidence: Seven depends on complete epoch boundaries; unknown reset loss remains unknown.
Decision to make: Count 3 events before reset plus 4 after reset, yielding 7; hold reconstruction if the pre-reset boundary is missing.
Use the downloaded brief as planning input. AI suggestions remain proposals; review scope, owners and acceptance evidence yourself.
Filled review note
Invented planning text. Adapt it to your evidence and confirmed owners.
Epoch note: 3 before reset plus 4 after reset equals 7 under complete boundary evidence. If the pre-reset count is unknown, the exact total is held.
Put the outline to work
- Inspect whether the measure is cumulative or a current-state gauge.
- Separate epochs at known resets.
- Sum only evidenced within-epoch increments and disclose missing boundaries.
From a useful outline to team work
Explore TeamBoostAI for your team
Bring this manual reporting policy and its owned checks into your TeamBoostAI work discussion. Native report/export fields and historical reconstruction depend on your account and implementation; this worksheet does not import or change product records. Confirm the workflows available in your account before adopting this outline.
Request TeamBoostAI access
Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.
A practical decision workshop
Inspect the example before choosing a rule
Trace an invented case, preserve the evidence limits, then adapt the manual worksheet to your own decision.
Evidence dependency diagram
What must be known first?
Scroll the diagram sideways if needed; every dependency is also written below.
- Complete epoch 1 → Period increments: 3 events.
- Complete epoch 2 → Period increments: 4 events.
Synthetic example · not customer data
Inspect the records
| Observation | Counter epoch | Count |
|---|---|---|
| Period start | Epoch 1 | 10 |
| Known pre-reset boundary | Epoch 1 | 13 |
| Reset | Epoch 2 | 0 |
| Period end | Epoch 2 | 4 |
Wide tables scroll sideways on small screens.
Download records (.csv) · Download complete decision kit (.json)
Decision explorer
Choose an evidence situation
This returns a written example explanation. It does not inspect your records or approve a real report.
Read every situation without the interactive tool
- Both epoch boundaries are known and complete
- Show the separate increments and their sum.
- A pre-reset observation may miss increments
- Report known observations and hold the exact period total.
- The value can freely rise and fall
- Treat it as a state observation, not this cumulative counter policy.
Version comparison viewer
Keep the draft and its correction visible
Draft or earlier version · review its limits
Draft: period count 4−10=−6.
Revised example · limits retained
Epoch note: 3 before reset plus 4 after reset equals 7 under complete boundary evidence. If the pre-reset count is unknown, the exact total is held.
| Review boundary | Draft to review | Revised example |
|---|---|---|
| Epoch handling | One subtraction across reset | Separate within-epoch differences |
| Coverage | Missing observations silently assumed complete | Exact reconstruction requires complete boundaries |
Wide tables scroll sideways on small screens.
Questions about this workflow
Why not subtract 4−10?
Those endpoints belong to different counter epochs. Their negative difference is not a negative completion count.
Can I assume the last sampled value was the pre-reset total?
No. If observations missed increments, exact reconstruction is unavailable.
Does this create tasks in the product?
No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.