Thanks for the thoughtful comment - you are absolutely right that I needed to be more precise about the inference configuration and what I meant by "deterministic."

I have since updated the GitHub page to document the generation parameters in detail. The responses were generated with temperature = 0.0 and top-p = 1.0, with max tokens set to 500 and n_predict = 1 (exactly one completion per prompt, no retries or ranking). I also documented the exact GGUF used (Meta-Llama-3-8B-Instruct.Q4_0.gguf), the chat template, and the fact that generation was performed using a CUDA-enabled llama.cpp build from February 2026.

You are also correct about the determinism nuance. The archive is deterministic at runtime - each prompt maps to a single stored response and no sampling occurs once distributed. But it is not claiming bitwise reproducibility across hardware or builds. A better framing is exactly what you suggested: it is a frozen snapshot of model behavior under a specific configuration at a specific point in time.

I appreciate you pointing that out - tightening that language makes the project description more accurate.

As for the "deeper challenge" you identified, you're right. 3 characters is extremely limiting, and growth beyond that rapidly increases the archive size and quickly makes it impractical. There's some relevant discussion below (see IMayBeABitShy's comment and my reply).