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 #57
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 #57
20-sys.db · systems/20-builder/data/
id
57
system
date
08/21/26
subject
approved_by
USR369 David
se_id
—
tr_id
—
_rowid
57
detail
Added multi-system support (comma-joined chip picker, + Add button) and a new NAME OF TASK field (separate from the existing TASK # code field) to the FIX-LOG web editor at backend/tools/fix-log.html. Log line format bumped systems/governance/FIX-LOG.md and its governing SOP-FIX-LOG.md from 5-field to 6-field: date/time | system(s) | T### | name-of-task | status | fix. Backward-compat parser (parseLineParts) auto-detects 4/5/6-field legacy vs current lines by field count and whether field 4 is a status keyword. Root cause of TASKGATE matched:false on the original request: SOP-FIX-LOG.md existed live at systems/governance/SOP-FIX-LOG.md since 08/12/26 but was never listed in SOP-INDEX.md, so TASKGATE's SOP-INDEX-based matcher could never have surfaced it. Fixed by adding it to SOP-INDEX.md (bumped to v2.8) instead of writing a duplicate SOP, per the NO PER-SYSTEM DUPLICATE SOPs rule. Also corrected a stale path claim in SOP-INDEX.md's existing FIX-LOG.md data-file entry (it said USR369/FIX-LOG.md; the real, live, populated file is at systems/governance/FIX-LOG.md). File backed up via BACKUP.php file-mode before editing (backups/20-builder/html/Builder_FixLog_CURRENT.html). All three files grew in size on write (no shrink-guard trigger).
▼ Show timestamps
created_at
2026-08-21 11:47:47
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