yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 50-sys.db
systems/50-daily/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
50-sys decisions Row #5
Tables
decisions
18
domain
0
events
200
gov_archive
0
gov_archive_fts
0
gov_archive_fts_config
1
gov_archive_fts_data
2
gov_archive_fts_docsize
0
gov_archive_fts_idx
0
items
8
sessions
38
sqlite_sequence
5
transfers_log
6
decisions — Row #5
50-sys.db · systems/50-daily/data/
id
5
system
date
08/31/26
subject
Built SOP-STANDARD-MILEAGE.md - odometer fallback estimates for recurring routes
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
5
detail
USR369 requested a way to log recurring routes (gym, Grandma's, Costco) with standard mileage when he forgets to give an odometer reading. TASKGATE matched SOP-HOUSEKEEPING-SCHEDULE.md but content review showed it's about unrelated platform file-sweep cadence - treated as no real match per protocol, wrote a new SOP-STANDARD-MILEAGE.md, added to SOP-INDEX.md, broadcast. Set a 3+ confirmed-sample threshold before a route qualifies as a usable fallback, to avoid estimating off a single lucky data point. Computed actual averages from Daily's full events history: Home<->EOS Redlands qualifies (23mi avg, 5 samples, range 22-25). Montclair (41mi, 2 samples), Costco Highland (17mi, 1 sample), EOS Ontario (41mi, 1 sample) don't meet the bar yet. Grandma's has no isolated sample at all - always combined with an EOS Montclair stop on every trip on file. Standard figures written to knowledge-50.md, will grow as more real readings come in.
▼ Show timestamps
created_at
2026-08-31 13:52:00
Backend Domains Panel DB Viewer Transfers
Backend Tools DB Viewer DB Admin Server Map File Editor Backend Tools DB Viewer DB Admin Server Map File Editor