If you are new to Trellis, start with What is Trellis?. These concept pages go deeper on runtime authority, service boundaries, transport surfaces, resources, and generated APIs before you write a service, app, device, or CLI.

• Architecture: service categories, platform boundaries, and why APIs stay with the services that own them.
• Contracts: service and app contracts, contract identity, and generated artifacts.
• Deployment authority: deployment authority, identity authority, authority updates, reconciliation, availability, liveness, grant overrides, and contract evidence.
• Communication: RPCs, operations, events, feeds, and cross-contract dependencies.
• Authentication and authorization: principals, sessions, portals, approvals, and capabilities.
• Resources: KV buckets, stores, public app state, and runtime streams.
• Files and transfers: public file APIs, service-owned stores, and operation-native byte transfer.
• Type system and errors: schemas, validation, declared errors, Result, and expected failures.
• Devices and activation: preregistered devices, device deployments, activation portals, review policy, and online credentials.
• Jobs: service-private background execution and when to use operations instead.