ElastOS is a local-first Runtime for Apps and services. Home is the user-facing front door. Runtime derives identity and authority, routes typed resource requests, owns lifecycle and audit, and delegates provider-backed operations to the provider that owns their semantics.
Executable capsules request typed Runtime resources. Components use
elastos:bus@v1; web projections use narrow Runtime adapters. Carrier is an
endpoint-authenticated off-box transport selected below that boundary. It is
not the capsule API and does not by itself prove application-message
authorship.
For people, Carrier is how Homes reach each other. Homes connect directly, by identity, and a new Home needs one introduction to join the network. Joining Community lets other members send you Community posts and contact requests; it gives them no access to your files, apps or data, and direct messages need your approval of the contact.
Use these documents as the sources of truth:
- Principles: stable implementation constraints.
- GitHub issues: verified behavior, known limitations and open work.
- Architecture: trust boundaries and component ownership.
- Capsule model: package, execution, and isolation model.
- Capsule authoring: checked manifest and template path.
- Namespaces: rooted local and content identities.
- Command matrix: user, operator, and no-Runtime command lanes.
- Documentation index: the complete active documentation map.
Release readiness is tracked by the source and release checklist. This overview does not declare a feature, target, or release accepted.