runtime · today · Should AI memory hold credentials?
Memory is context. Vault is secrets.
No. Memory is approved work context. Vault holds credentials. Secrets never mix into ordinary memory. Vault extraction requires explicit approval and never prints secret values. Keep the two planes apart. That is Control on TARX_OS.
Keep the two planes apart. That is Control.
TARX works privately on your computer. Connections stay off until you allow them.
Product proof. Not atmosphere. TARX_OS on silicon you own.
HOW TARX WORKS
How TARX works with Memory and Vault
Literacy starts here. Teams paste API keys into chat history and call it memory. TARX splits the planes. Memory is context you approved. Vault is secrets. Extraction waits on Deny or Allow and never prints the value.
Web lookup is labeled Evidence. It does not land in Memory unless you say remember. That is how a private runtime stays private when someone turns search on.
Same split on a Mac, a T-4, a T-7, or a T-70. Hardware does not get to be sloppy with secrets.
THE STACK
Join the Supercomputer. Or own Private Hardware.
TARX_OS on computers you already own. Supercomputer hardware when the site needs dedicated NVIDIA.
Placeholder
TARX_OS · Conversation into the runtime · free software
Not unless you say remember. Web lookup is labeled and stored as Evidence.
Can Vault print a secret into the transcript?
No. Extraction never prints secret values.
Is Memory encrypted storage for keys?
No. Memory is context. Vault is secrets.
Does this change on Supercomputer hardware?
No. Same Control contract.
TWO EQUAL PATHS
JOIN THE SUPERCOMPUTER. OR OWN PRIVATE HARDWARE.
Join the Supercomputer. Or own Private Hardware.
JOIN · TARX_OS
Join the Supercomputer
Give TARX superpowers.
TARX works privately on your computer. Connect to the Supercomputer when you want TARX to research the web, use more skills, and take on bigger jobs with deeper models. Supercomputer connection is in beta, and capacity is being qualified.
