Mandate
The TARX Mandate
AI should be free to start, private by default, powerful when needed, and controlled by the person or organization using it.
01
TARX starts free.
The base layer belongs on your computer. TARX should be useful before a subscription, before procurement, before permission.
02
Local comes first.
Your computer is not a thin client for someone else's intelligence. TARX begins locally and routes outward only when the work requires more power.
03
Power is optional.
Supercomputer is not the product tax. It is the power layer. Use what you need. Give what you can. Pay for the difference.
04
Memory belongs to the user.
AI should remember the work that matters without turning private context into platform property.
05
Memory is not Vault.
Preferences, decisions, project context, and operating assumptions belong in memory. Credentials, API keys, tokens, SSH keys, private keys, passwords, passcodes, and secrets belong in Vault.
06
The cloud should be approved, not assumed.
Hosted compute should be intentional. TARX should make local, Supercomputer, and private enterprise routing visible and governable.
07
Tools should act with consent.
TARX can answer. TARX can also act. The difference matters. Sensitive actions require policy, approval, and evidence.
08
Enterprise needs control, not another chatbot.
Organizations need memory, files, models, tools, routing, policy, evidence, deployment control, and support under their own rules.
09
Compute should be earned as well as bought.
TARX is not here to recreate token rent. Useful compute contribution should create access back into the network.
10
The user is not the fuel.
The user is the operator. TARX exists to remove demand from attention systems, not add another one.
