Vakend is easiest to understand as five public layers. These are responsibility boundaries, not a disclosure of private modules.
flowchart TB
Human["Human intent"] --> UX["Applications & visible approvals"]
UX --> Capability["Capability and policy boundary"]
Capability --> Local["Local vault, runtime, models & devices"]
Capability --> Peer["Trusted peer network"]
Capability --> Optional["Optional external providers"]
Local --> Evidence["Audit, health, recovery & evidence"]
Peer --> Evidence
Optional --> Evidence
Evidence --> Human
| Layer | Public responsibility | User benefit |
|---|---|---|
| Applications | Explain a job in human terms and present its controls | One place to understand and perform a task |
| Capability boundary | Limit what an app or automation may do | A compromised or mistaken component should not receive ambient authority |
| Local foundation | Hold encrypted data, identity context, models, and device services | Useful work can continue without making the cloud the default owner |
| Connections | Reach trusted peers or explicitly selected services | Collaboration remains possible without hiding where data goes |
| Assurance | Surface health, logs, recovery, tests, and policy | Users and operators can challenge claims and recover from failure |
flowchart LR
Core["Identity · Vault · Runtime"] --> Personal["Personal workspace"]
Core --> Comms["Communication & network"]
Core --> AI["Intelligence & automation"]
Core --> Trust["Security · Governance · Recovery"]
Core --> Learn["Learning & research"]
Core --> Money["Wallet · Markets · Administration"]
Core --> Build["Developer · QA · Distribution"]
AI --> Personal
AI --> Learn
Trust --> Comms
Trust --> Money
Build --> Core
Connections describe possible cooperation. They do not mean every app can freely read every other app. The Application Tree documents each app’s intended neighbors.