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 #157
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 #157
10-sys.db · systems/10-master/data/
⌂ Master Hub →
id
157
system
10 Master
date
08/21/26
subject
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
157
detail
Ran the real systematic sweep USR369 asked for, scoped to the Core Five (00,10,20,30,40) per his direction, rather than continuing to react to breakage one file at a time. METHOD: no server shell access available, so used RESTORE.php's snapshot-based action=list (walks today's platform ZIP) to enumerate real files directory by directory -- backend/tools/, backend/tools/critical/, backend/tools/html-debug/, backend/sys-com/, backend/ed/, backend/migration/, backend/api/critical/, systems/commands/, each of the five systems' own root + toolbox/ directories, and frontend/ (including the two Builder-A/Builder-B subsplits). Filtered to PHP/JS/HTML candidates (93 files), checked each via file-reader.php for the literal retired-token string. RESULT: 29 of 93 files (31%) still had the old token hardcoded -- far more than the 16 found across three earlier reactive passes today. This confirms the earlier reactive approach was fundamentally undersized; a full sweep was the right call, not overkill. Notable finds: all 5 systems' own index.php files (00/10/20/30/40) had it in client-side JS fallback constants. backend/sys-com/ (the dashboard/panel/traffic/schedule/kill-switch tool cluster) had it in 9 separate files. Several ad-hoc one-off admin scripts in systems/00-admin/toolbox/ (add_description.php, backfill_desc.php, boot_fix_addtask.php, boot_read_infoindex2.php, boot_verify_info.php, diag_pick.php, inject_stubs.php, testcl_boot.php, wipe_tmp.php) -- these read like debugging/one-time-fix scripts accumulated over time, each with its own inline auth check. Also backend/api/critical/records-api_PREVIOUS.php (a backup file, still technically readable) and systems/10-master/toolbox/master-tool.php. Backed up all 29 (grouped by owning system, 6 BACKUP.php calls), patched (simple literal swap old->new, all were plain hardcoded-constant patterns, no architectural change needed), redeployed, then re-ran the exact same 93-file scan afterward -- confirmed zero remaining old-token occurrences across the full scoped set. NOT YET SWEPT: this covered the Core Five's own directories plus the shared backend/tools and backend/sys-com clusters -- it did NOT cover the 6 domain systems (50-Daily, 60-Finance, 70-Health, 80-Kitchen, 90-Inner, 95-Travel) own toolbox/data directories, nor backend/knowledge, backend/records, backend/web, backend/build-diary, backend/security, backend/docs, backend/standards, backend/projects, backend/sandbox, backend/logs, backend/info, backend/jobs, backend/config, or backend/369 -- none of those were enumerated or checked this pass. The full 3181-file snapshot is far larger than what was covered here.
▼ Show timestamps
created_at
2026-08-21 17:52:32
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