IDEA: bagit but checking if source has been casually tampered with since...

@mistersql

IDEA: bagit but checking if source has been casually tampered with since installation, i.e. sign each file, put it in a file checker and then on startup check if files were tampered with.

Opinion, security geeks poo-pooing anything that looks like security theater is hampering creating security models for agentic LLMs. You only need a solution that is difficult enough to circumvent that the SotA model can't casually crack it with typical token limits.

Self-replies

I don't want to run every integer object in its own docker container. (This is an honest to god idea I heard on a podcast decades ago, except it was running every object in a WCF webservice, good isolation, now you can run two integers on your 1TB of memory laptop, safe from NK hackers)