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
I0839
watch inherits every doctor fix and its own budget
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Confirm watch dispatches the rewritten validators, time it, and declare benchmark.budget.watch_ms next to doctor's.
- Why
- watch shares the validators, so it is fixed by the same work, but nothing proves it.
- Now
- watch takes 9.7 s.
- Wanted
- Under 1.5 s on this repository, reported against its budget like doctor.
- Done when
- unknown: the record declares no `completion`
- Risk
- watch reports drift, so the budget finding is INFO there, never DRIFT.
Acceptance
- watch prints its total and budget
- Case 83 covers watch as well as doctor
- Validation
MJ_TIMING=1 bin/majordomus watch- Evidence required
doctor_under_budget- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/watch.sh.ai/repo/policy.yamlshare/allow/policy.txtshare/skeleton/policy.yamltest/cases/83_doctor_budget.sh- Not
- none
- Depends on
- Priority
- p0
- 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-05
- Updated
- 2026-09-05
- 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.