Files
felhom.eu/documentation/audits/end-dates-list-2026-11-11/tools/table-head.md
T
admin 978666dde3
gates / gates (push) Successful in 2m2s
lists: the Clock list (70 jobs) and the End-dates list (39 things), 9 register rows, 4 decisions
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
2026-11-11 11:54:42 +01:00

2.8 KiB

The End-dates list — the table

Built 2026-11-11 from the source of the four repositories, from read-only measurements on the three test boxes (Tester 1, demo-hp, the N100; host and guest) and from what any visitor can read with no login. One block for each thing that stops working, or stops being safe, on a date or after an age. 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 of 2026-11-10: DooPlex and ep0, and every account (Cloudflare, Hetzner, the mail service, the registrars). What this table says about them comes from the repository's own scripts and documents.

The eight questions: 1 what it is, who owns it, where it lives · 2 when it ends (a real date for each box where one was measured, else the rule) · 3 who renews it, and how long before · 4 what breaks, and for whom · 5 who is warned before the end · 6 a box that was off past the end date: does it come back by itself? · 7 what happens if the renewal fails · 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?

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…S23; controls in the same file). Every N names its class row: T1 = R-1379 an end exists and nobody is warned before it · T2 = R-1380 another party renews and our pin does not follow · T3 = R-1381 no document says when it ends, or where to read the date · T4 = R-1382 a box that was off past the date: nobody knows if it comes back.

Who read what. A cell whose mark is D, K or N, and every A that tools/marks.py carries, holds the main session's words: the pointer was opened and read. Every other cell holds a helper's words with the mark A: tools/resolve-helper.py opened each of its pointers (the file and the line exist, and the name the helper gave stands at that line). 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 end date?): NAMED and MENTIONED with a pointer were read in the documents. Where the line says "a machine count", the status comes from a search of the architecture folder: 0 lines = UNNAMED, else MENTIONED.