Work items
133
in 2026-08-27 → 2026-09-26
Completed
1
candidate completions, not acceptances
People with tasks
0
humans only
Notion evidence
4
4 docs · 0 comments
No task tracker is connected, so nothing on this page is an independent acceptance.
- No task tracker connected — work units derived from merged pull requests.
- No estimates: commitment reliability and estimate accuracy cannot be computed.
- No acceptance criteria: the LLM cannot verify delivery against a definition of done.
- No requested-at timestamp: lead time is unavailable; cycle time starts at PR open, not at work start.
- Evidence confidence capped at 0.55 — below the 0.6 floor, so no composite score and no alerts.
Where work is defined
Sources are not interchangeable. Each row states what that source, as actually populated, cannot answer.
| Source | Items | Assigned | Completed | Estimates | Due dates | Criteria | Cannot answer |
|---|---|---|---|---|---|---|---|
| github Derived from pull requests. Confidence capped at 0.55. | 133 | 0 | 1 | — | — | — |
|
Tasks by person
Counts, not a ranking. Closing ten trivial items beats finishing one hard one, so task volume is never scored on its own — read it beside difficulty and evidence.
No task is assigned to a mapped person in this window.
Notion evidence
Writing is work, and it is invisible next to code unless something counts it.
Documents
4
0 authors
Comments
0
0 people · full history
Pages last edited
4
one per page — not an edit count
Unattributed
8
no Notion identity mapped
Read page edits carefully. Notion’s API exposes only last_edited_by — one record per page naming whoever touched it most recently, with no history behind it. A page edited forty times by four people produces a single row. That number can answer “who touched this last”; it can never be summed into “edits made”, and it would understate every collaborator except the last. Comments carry full history and are safe to count.