yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 10-sys.db
systems/10-master/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
10-sys decisions Row #113
Tables
decisions
198
domain
8
events
0
gov_archive
0
gov_archive_fts
0
gov_archive_fts_config
1
gov_archive_fts_data
4
gov_archive_fts_docsize
0
gov_archive_fts_idx
2
items
18
sessions
99
sqlite_sequence
5
transfers_log
0
decisions — Row #113
10-sys.db · systems/10-master/data/
id
113
system
date
08/04/26
subject
Closed the loose end from T632's own close note -- jurisdiction.db owner_decade for Travel
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
113
detail
T632 (Travel system-code unification) was already closed 07/25/26 with a real root-cause fix in roster_lib.php. Its own close_note flagged one unfinished piece: jurisdiction.db still showed owner_decade=10 for Travel, needing re-registration. Verified this was still true (not assumed) by locating jurisdiction.db at systems/community/jurisdiction/jurisdiction.db and querying it directly -- found 5 stale records (J076/J098/J099/J100/J101), all dated to original 07/15/26 creation, never touched by the 07/25/26 fix. Backed up jurisdiction.db first (byte-verified copy). Corrected all 5 records' owner_decade from 10 to 95, fixed J076's item_name label (was literally 'Travel [10]'), appended a correction note to each row rather than silently overwriting history. Verified via read-back query -- all 5 now show owner_decade=95. Also corrected an assumption I'd made earlier in this session -- I initially treated T632 as still open based on a stale personal summary; it was not, the platform's own record was already correct and already closed with a real audit trail.
▼ Show timestamps
created_at
2026-08-04 09:04:07
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