Read-only review of every job on a timer and of everything that ends on a date, with measurements from the three test boxes. Nothing ends in the next 14 days. Register 236 -> 245 (R-1379..R-1387), pointer lines on twelve rows, D76-D79 in STATUS.md. Part C: felhom-agent's clone address holds no token now; the other clones wait for the operator's yes. R-1035's 4-week check moved to 2026-11-18 (operator read needed). Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
3.2 KiB
The Clock list — the table
Built 2026-11-11 from the source of the four repositories and from read-only measurements on the three test boxes
(Tester 1, demo-hp, the N100; host and guest). One block for each job that a clock starts: the night steps on a box,
the interval jobs, the watchdogs, the hub's daily jobs and its 60-second sweep, and the timers on DooPlex and ep0.
tools/make-table.py writes this file from the helpers' answers (evidence/helpers/) and from tools/marks.py; do
not edit it by hand.
NOT MEASURED, by the operator's ruling: DooPlex and ep0, and the hub's database. What this table says about the hub's jobs and about the timers on those two machines comes from the repository's own source, scripts and documents.
The eight questions: 1 what runs, who owns it, what starts it (with CUSTOMER, TEST-ONLY or OPERATOR) ·
2 when, how often, in what order · 3 how long it takes (measured where a box shows it), its time limit, and 10 or 100
times the data · 4 what happens if it does not run · 5 it runs late, or twice, or meets another job (the lock is
named) · 6 the clock is wrong or jumps · 7 who is told, and when · 8 how do we know (MEASURED, a test, SOURCE, a
document, or nobody knows). A ninth line, outside the marks: is the hand step written in a runbook?
Every measured duration comes from a small test store (three boxes, a few apps, one night of controller logs). No number in this table says how long a job takes on a full household disk.
Marks: A answered, with a pointer · D decided, not built · K known gap, with its row · N nobody asked — it
survived the searches in EV/searches.txt (S01…S25; controls in the same file). Every N names its class row:
W1 = R-1383 a job does not run, gives up, or loses its state at a restart, and nobody is told · W2 = R-1384 a
verdict or an "already ran" check trusts a clock that can be wrong · W3 = R-1385 two jobs can meet with no lock and
no order · W4 = R-1386 no time limit and no measured duration · W5 = R-1387 a document and the source disagree
on a time.
Who read what. A cell whose mark is K or N, and every A that tools/marks.py carries, holds the main
session's words. Where its pointer was opened by eye, the pointer is written out in tools/marks.py; where
tools/marks.py shows +, the pointer is the helper's and tools/resolve-helper.py opened it (the file and the line
exist, and the name the helper gave stands at that line). Every other cell holds a helper's words with the mark A.
The main session read every helper answer to questions 4 to 7; it did not open each of their pointers. Treat those
cells as a map, not as proof.
Pointers: AG/ = felhom-agent/ · CT/ = felhom-controller/controller/ · CAT/ = app-catalog-felhom.eu/ ·
HUB/ = felhom.eu/hub/internal/ · E/ = felhom.eu/ · AR/ = felhom.eu/documentation/architecture/ ·
RB/ = felhom.eu/documentation/runbooks/ · EV/ = this folder's evidence/. tools/check-pointers.py prints the
text behind each one.
Named status (does an architecture document name this job?): the status comes from a search of the architecture
folder: 0 lines = UNNAMED, else MENTIONED. It is a machine count, not a reading.