yttcom.net
Backend / Tools / DB Viewer
yttcom.net
Domains / DB Viewer
v2.0 · 07.11.26
◇ 60-sys.db
systems/60-finance/data/
records.db inbox.db transfers.db knowledge.db jurisdiction.db
60-sys decisions Row #53
Tables
decisions
60
domain
0
events
42
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
122
sessions
32
sqlite_sequence
4
transfers_log
0
decisions — Row #53
60-sys.db · systems/60-finance/data/
⌂ Finance Hub →
id
53
system
60 Finance
date
08/24/26
subject
June 2026 expenses gap resolved as false alarm; events-table duplication found and reported
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
53
detail
USR369 asked to check on Daily's claimed resend of 33 June 2026 records. Verified via Notion query (33 rows, dates 06/07-06/30/26 matching exactly). Cross-checked Finance's own items table and found all 33 already existed there before this session (ids ~88-103) - the same rows I'd already backfilled into Notion on 08/21/26. Root cause: SOP-DAILY-INTAKE.md's history section flagged this as a gap based on an unconfirmed TRANSFER status, not actual missing data - Daily's live DB never had it (true) but Finance's items table did the whole time. Daily then cross-system-wrote the same 33 rows into Finance's own events table (events count 4->42, +38 not +33 as claimed), creating duplication across items/events/Notion. Could not safely dedupe: Finance's data/api.php has no get_events/list_events action, so event row IDs can't be discovered to trash them. Reported both the missing API action and the count mismatch to Server[40] (msg 1151). Also corrected two stale knowledge-60.md WISDOM entries that would have kept falsely re-flagging June as a gap at every future open.
▼ Show timestamps
created_at
2026-08-24 08:29:35
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