memory + vault
What TARX can remember
Learn what belongs in ordinary memory, what needs approval, and what should never be stored there.
TARX memory should be useful, bounded, and reviewable. The product should teach the model and the user what belongs in memory as work unfolds.
Good memory
Good memory is durable work context that improves future help without exposing secrets.
- Project names and goals
- User preferences
- Workflow decisions
- Reusable instructions
- Team conventions
Bad memory
Bad memory is sensitive material that should live in Vault, remain ephemeral, or require a stronger approval boundary.
- Raw credentials
- Private keys
- Passwords
- Sensitive customer data without policy
- Unreviewed regulated records
Operating principle
When in doubt, ask for approval, store less, and keep the route evidence clear.