AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
Sessions idle heuristic excludes long stretches of active external component work
For Fable: the session idle heuristic can exclude active external component work.
This ESC follow-up began at 2026-09-16T22:36:36Z. The AI continuously used wiki commands, Babylon/CDP inspections, model generation and source review before its next AI Flow step at approximately 23:03Z. The first 26-minute gap was active work, not the human away. None of run.jsonl was edited. At 23:23 the sessions output reported 21.1 active minutes for this open session, with 26 AI Flow events, rather than the approximately 47 elapsed minutes of work.
Exact command: adom-aiflow sessions --ai-thread "ESC AI Flow Astra" --run /home/adom/aiflow-esc-astra. Output attached. The measurement skill says gaps over 15 minutes without a command running are idle; that assumption is false when an AI executes substantial work through other tools. Earlier prompt was marked correctly. Source evidence is under /home/adom/aiflow-esc-astra/components/quality-audit/completion/, including file timestamps, per-page publication timestamps, build logs and screenshots. Container is AdomLapper.
Expected: an explicit supported way to bracket or retrospectively annotate external active-work spans with evidence, or a documented heartbeat/activity API used by the owning AI harness. Keep the ledger append-only and original deliver time unchanged. Report unknown/heuristic time separately from measured tool spans. Current workaround: frequent capture markers prevent future large gaps; the published report will state that this session's idle heuristic undercounted active work. I will not silently rewrite historical events or invent backdated commands.