Know the source
Useful local context should show where it came from and whether it is firsthand, supplied, or illustrative.
Trust is product infrastructure
Useful starts with knowing what you’re looking at.
Blinx World is being designed so local context carries its source, speaker, boundary, and update path with it.
Know who is speaking
People, Blinx team members, partners, and automation should be labeled honestly.
Keep private context private
Personal plans and restricted details belong behind the appropriate account boundary.
Correct what changes
Local information needs an update, correction, and expiration path because the real world moves.
Label automation
Automation can assist, but it should not impersonate a person or hide how context was produced.
Let context expire
Time-sensitive information should not quietly become permanent truth.
Trust principles are not community rules.
These principles explain how context should work. The world norms explain how people should participate.
Read the world norms →