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 #26
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 #26
10-sys.db · systems/10-master/data/
id
26
system
01
date
07/09/26
subject
D118 — Protected paths guard + exact-path deletion logging
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
26
detail
05-Front_end disappeared from the server on or around 07/08/26, likely during Server Session 006's cleanup pass which logged '9 orphan dirs moved to backend/trash/' — but no corresponding trash folder from that date exists anywhere, and the log never named which 9 directories. This meant there was no way to confirm or deny whether 05-Front_end was one of them. David restored 05-Front_end via direct FTP upload; root cause remains unconfirmed. To prevent recurrence: CLEAN.php v1.1 now actively verifies 6 protected top-level paths exist every time it runs (05-Front_end, backend, systems, transfers, backups, .well-known) — fails loudly and lists exactly what's missing if any are gone, rather than relying on someone noticing via FTP days later. Also added log_deletion_action() — any future CLEAN/purge action must log exact paths to backend/sys-com/deletion_log.md, not just a summary count. This does not retroactively explain what happened on 07/08 — that remains an open question for Server to investigate — but it closes the detection gap going forward.
description
D118 — Protected paths guard + exact-path deletion logging
▼ Show timestamps
created_at
2026-07-09 06:40:57
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