Personal context exists to serve the person it belongs to. Enti’s architecture, interface, and business model should preserve their control over the information that matters to them.
Principles
Built around people, not platforms
These principles shape how Enti is built today and what it should remain as it evolves.
01
Control stays with the person
02
Local by default
Personal data should remain, by default, in a space controlled by the person it belongs to. Network services may extend what Enti can do, but they should not become a requirement for accessing one’s own context.
03
Privacy is an architectural choice
It should always be clear what data exists, where it is stored, and why it is transmitted. Promises of privacy are no substitute for architecture that actually provides it.
04
Dependencies must earn their place
Enti does not reject external technologies, but it avoids unnecessary dependencies. Every new dependency should provide clear value and have acceptable consequences for control, resilience, and independence.
05
The future should not be presented as the present
What already works should be described as a current capability. What is still being explored should be presented as a direction. Enti should not present a future personal AI as though it already exists today.
06
Quiet utility over engagement
A useful personal system should be there when it is needed without manufacturing urgency. A person’s attention is not a metric to be maximized.
07
Utility before expansion
Complexity is not progress in itself. New capabilities are worthwhile only when they make personal context more useful, more understandable, or more autonomous.
08
The business model should align with the user’s interests
Enti should be economically sustainable. Revenue should come from useful capabilities that people knowingly choose to pay for—not from selling their data, maximizing their attention, or creating artificial dependency.