Core What the Deva Core tracks inside every action, and the reference data behind it. Every Deva Core run is described by a small, fixed vocabulary. Each time something happens, the Core records which feature was involved, what was done, what state it is in, and what the intent was. The same names are used everywhere in the code, so a log entry means the same thing in every Deva. This reference is generated from the live data files shipped with the Core. Features (13): the built-in capabilities, such as License, Error, Log, Security and Support. Zones (44): where an action is happening, so activity can be traced to its location. Actions (93): what was done, such as consent, encrypt, decrypt, return. States (115): the condition something is in, such as online, active, idle, valid or catch. Intents (44): the purpose behind an action, such as good, bad or lawful. Beliefs (25): the stance recorded for the work, such as positive, productive or vedic. Events (25): the named signals the Core emits through its lifecycle, such as devacore:start, devacore:ready and devacore:error, which your own code can listen for. Messages (34): the standard text the Core uses for lifecycle steps and errors, so output is consistent and can be audited. Why it matters: these lists form the audit trail. Because every record uses the same fixed names, activity can be searched, verified and reported on without guessing what a label means.