Terminal Lucidity DB

Example web interface for Terminal Lucidity DB

GitHub exhibited at may 17 edition of FLIP TABLE;

Decaying message

The database keeps your canonical body bytes on disk (UTF-8 text, JSON, or opaque binary). Each lucid read only returns a frayed snapshot — here it is beside what was stored before that read wore the record down.

Stored (canonical) 

          

          

            Surfaced on last read here
            

            

          

        

      


      

        

          
Database file

          

            
            
          

          

            
          

          

            Uses TLDB_PATH on the server. Download copies the live file as-is.
            Wipe drops all rows (records, episodes, meta) inside that file using an
            exclusive transaction, then recreates tables — avoids half-deleted SQLite files leaving old
            rows visible (browser confirms first).
          

        


        

          
Insert record

          
          
        


        

          
Simulated time

          
          
        


        

          
            Request log
            expand for HTTP traces
          
          

            

              

                Time, method, path, status, ms, bytes. Errors show a body snippet.
              

              
            

            

          

        

      


      

        
Records

        
        

      


      

        

          
Lucid read

          
          
        


        

          
Last response body