Trust, Privacy & Evidence
TARX should show proof instead of theater.
Evidence model
| Evidence | What it should show |
|---|---|
| Route | Computer, Supercomputer, Enterprise/private, or unknown. |
| Approval | What the user approved and what remains blocked. |
| Files | What was inspected or touched. |
| QA | Commands and results when QA actually ran. |
| Persistence | Whether evidence is current-session or stored. |
Privacy model
Cloud AI sees prompts. TARX is designed to see the work environment, but it must still respect route boundaries, approvals, Vault handling, and what can be proven.
What TARX must not claim
- No unsupported “everything stays local” claim.
- No Supercomputer routing claim without route evidence.
- No private deployment claim without contract/deployment proof.
- No fake QA, files, Activity, or memory.