Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0304

Read the measurements back through the history surface, under a bound

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
Milestone status
BLOCKED
Wave
3
Waiting on
Holds back
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI0303I0303 is not DONE
milestoneexecution-telemetrythe milestone execution-telemetry waits on an outcome of its own
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0304

majordomus plan verify I0304

majordomus plan done I0304

What it is

Objective
Make recorded execution facts readable through the surface that already answers questions about past tasks, with the same retention bound the other durable stores carry.
Why
A measurement that can only be read by opening a file is a measurement nobody reads. It also has to be bounded, because an unbounded append-only store is exactly what this repository refuses everywhere else.
Now
Facts are recorded against tasks and can be read only from the record itself.
Wanted
History reports the measured facts alongside the task they belong to, says not_reported where that is what happened, and the store is capped like the ledger.
Done when
unknown: the record declares no `completion`
Risk
Showing per-task numbers invites reading a trend into them; the surface has to present facts without implying a series.

Acceptance

  • History shows measured facts and explicit absences for past tasks
  • The store has a declared retention bound and the bound is enforced by a case
  • No aggregate figure appears at this layer
Validation
bash test/run.sh
Evidence required
suite
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
libdocs
Not
Aggregation, averages or any figure derived across tasks; that is the next milestone
Depends on
Priority
p2
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.