Definitions of key architectural patterns, core ADL mechanisms, and regulated industry terms mapped in our domains.
A highly structured, declarative application definition format (defined in YAML) that specifies data models, relationships, field validation rules, role-based access control policies, state machine transitions, and automated workflows.
The domain-specific scripting and expression language used within ADL to specify database queries, computed properties, transition conditions, and permission rules.
Suspicious activity investigations and compliance reviews within financial systems, defined in ADL using immutable transaction records and audit event feeds.
Systems for verifying industrial equipment safety, monitoring inspection schedules, and blocking operations if certifications or permits are expired.
An append-only, chronologically ordered, and immutable ledger of every event, data mutation, and state transition captured by the Kalos runtime for compliance reporting.
Regulations requiring financial institutions to track, investigate, and report suspicious transactions. Mapped to state machine transitions in ADL.
An unbroken, validated chronological record of the sequence of custody, control, transfer, analysis, and disposition of physical assets or digital records.
A certification program developed by the US DoD to measure defense contractors' capabilities to protect sensitive defense information. Mapped to ADL RBAC policies.
Fields whose values are automatically evaluated and kept in sync by the runtime using AEL expressions based on changes to other related resource fields.
A software design methodology where the entire system architecture is declared as static configuration rather than procedurally written as application code.
A US regulation prohibiting lending discrimination. Mapped in underwriting ADL to force immutable adverse-action logging.
A system for digital tracking of scientific experiments and protocols. ADL maps this to enforce strict data entry and modification approvals.
A specification format that is read and executed directly by a software engine, preventing any drift between documentation and the actual running software.
A US organization regulating broker-dealer firms. Suitability and execution audit trails are declared via ADL rules.
US regulations governing the export and import of defense-related articles and services, enforced in ADL using location-based and clearance-based RBAC.
The compiled, high-performance C++ microkernel runtime that interprets ADL documents to serve web APIs, validate schemas, and run compliant application behavior.
A laboratory system for managing, tracking, and validating biological and chemical samples, protocols, and equipment.
The internal design of the Kalos runtime, isolating storage, routing, transaction management, and expression evaluation into sandboxed, high-performance components.
A formal protocol in industrial operations to review and authorize changes to facilities, personnel, or software prior to implementation.
A method of regulating access to computer or network resources based on the roles of individual users. In ADL, permissions can be defined at the resource, field, and state-transition level.
A document filed by financial institutions to report suspicious transactions. Automated in ADL via AML case state machines.
A regulation requiring a comprehensive tracking database for all orders and executions, implemented using ADL immutable order feeds.
Standalone, fully specified ADL application definitions provided by ISDG as starting points (e.g., polis, lims, blog, tickets, orders, cms).
A model of computation consisting of a set of states, a start state, and the transitions between them. In ADL, resource lifecycles are governed by strictly validated state transitions.
An authorized work instruction in industrial plants. ADL prevents work order initiation unless valid safety permits and certifications are verified by the runtime.