Runtime concepts
You can use the quickstart before learning the internal architecture. These terms help when reading compiler output or diagnosing a failed operation.
| Term | Meaning |
|---|---|
| Domain | The business data, actions, reads and rules you define |
| Aggregate | A business object with a continuing identity, such as a task or asset |
| Directive | A declared operation that plans changes to one or more aggregates |
| Intent | A named business action that can compose directives into an atomic operation |
| Law | The compiled, versioned domain rules used by the runtime |
| Workspace | The data, installed rules and change history held together by a participant |
| Generated client | Typed calls and reads produced from your domain |
| Kernel | The runtime component that checks and executes operations under the installed rules |
| Offer | A proposed change submitted to the runtime for validation |
| Refusal | A rejected operation with a diagnostic; it does not apply the proposed change |
| Custody | The retained workspace history and files used for synchronisation and recovery |
| Projection | The current readable state derived from the accepted history and rules |
From an action to a read
Section titled “From an action to a read”An application calls a generated method. The runtime checks the input, permissions and business rules. If accepted, it records the change and updates the local read state. If refused, the application receives a failure to handle.
Synchronisation exchanges changes between participants. Each participant applies the installed rules to the history it has. Offline work and sync shows this with a runnable two-device example.
Changing the domain
Section titled “Changing the domain”The compiler records stable declaration identities in nomos.identity.usda. Keep that file with your source. A change to a field’s type, identity or merge policy may require an explicit evolution.
Compilation checks the authored model. Application tests check business behaviour. Deployment and compatibility checks establish whether a particular workspace and client can use a release. Passing one of those stages does not establish the others.