Declare it per workload
Record the class, readable surfaces and key locations for each workload. An encrypted app and its automation service can have different classes.
Trust
CARLOS was extracted from Eleven Messenger, which put security first. Not all apps need end-to-end-encryption, but arguably most apps should at least isolate tenants. The CARLOS Trust model lets you classify your apps so that you and others can quickly identify the trust model of a particular app.
What can the host see?
| Class | Model | What stays readable |
|---|---|---|
| S | Stateless | No stored user data. |
| A1 | Host-blind | Network timing and object sizes. Content keys stay on users’ devices. |
| A2 | Host-blind, declared metadata | Only the metadata the app explicitly declares, alongside transport information. |
| A/pub | Public by design | Public content is readable. Private content stays encrypted. |
| B | Sealed at rest | The running process can read data. Stored copies outside it remain encrypted. |
| C | Host-sighted | Stored data is readable. Protection comes from tenant isolation and operator policies. |
The A variants describe different models, not a ranking.
Your licence is a separate choice
Trust describes access to data. A software licence determines who may run, change and redistribute the code.
Make room for people and agents
Publish the tools and skills people can use to operate or adapt your app. Declare what is available today.