yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 20-sys.db
systems/20-builder/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
20-sys decisions Row #58
Tables
decisions
77
domain
0
events
0
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
5
sessions
47
sqlite_sequence
4
transfers_log
2
decisions — Row #58
20-sys.db · systems/20-builder/data/
id
58
system
date
08/21/26
subject
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
58
detail
Landed PEEK.php (read-only cross-system status snapshot: COMMS open/closed, inbox/transfers pending counts, gov file freshness) that CC[100] had built locally but couldn't reach the server for. CC provided no attachable file content this session, so rather than block on file transfer or guess at its exact source, rebuilt it directly on the server matching CC's stated design (?system=all|decade, read-only-enforced) and platform conventions confirmed by reading CHECKPOINT.php and inbox-api.php source (auth-lib.php token check, roster_lib.php for the system list, direct SQLite3 prepared-statement queries against comms.db/community.db/transfers.db instead of calling inbox-api.php's pickup action, which has a side effect of marking items seen -- PEEK must never mutate state). Deployed first to systems/commands/PEEK.php per the intended path -- that path returns HTTP 403 for every request regardless of query string, confirmed to be path-specific (not a PHP error) since the same content at backend/tools/critical/PEEK.php returns 200 clean. Logged as K391 for Server[40] to investigate; left a DEPRECATED stub at the original path pointing to the working one.
▼ Show timestamps
created_at
2026-08-21 15:35:05
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