Execution Model
Execution Principle
In MySirt the system is not implemented — it is derived.
Applications are not written directly in code. They are derived from structured models expressed through the execution meta-model.
A formal definition describes data, behavior and responsibilities. The Execution Engine interprets this definition and produces the operational system that enforces it.
The running application remains a direct consequence of the model, not a separate artifact evolving independently.
Executable DSL Foundations
Core Definition
The MySirt DSL is a declarative language used to define complete operational information systems. It describes system structure, behavior and organizational rules within a single formal definition.
System Dimensions
A MySirt model defines three fundamental dimensions of a system:
- Structure — entities, fields and relationships
- Behavior — triggers, jobs and operational rules
- Organization — roles and access policies
Together these elements form the executable specification of the application.
Model Instead of Code
The DSL describes what the system must do, not how it is implemented. The Execution Engine interprets the model and generates the Executable Information System.
Complete Systems in One Definition
A complete business system can be defined within a single DSL file. The definition includes data structures, workflows, security rules and user interaction structures required by the application.
Operational Behavior in the Model
Triggers and jobs allow the DSL to model operational workflows directly within the system definition.
Business logic is expressed declaratively without procedural implementation.
Execution Model Principle
The DSL acts as the executable model of the system. The engine derives the runtime application and enforces the rules defined in the specification.
Clarity emerges through execution.
Define the Domain Model
- Entities and relationships
- Business rules
- Roles and permissions
- Workflow logic
Execute the Model
- Model is interpreted
- Structures are validated
- Dependencies are resolved
Operational System
- Executable environment derived from the model
- Behavior enforced by definitions
- Responsibilities embedded in the system
Iterate Structurally
- Modify the model
- Regenerate the system
- Maintain structural coherence
Continuous Model Operation
The generated system is not a final artifact. The operational environment remains derived from the model throughout its lifecycle.
System evolution happens by modifying definitions rather than modifying implementation.
Structural Regeneration
Changes at the model level propagate coherently to the system. The model remains the single Source of Truth.
Model as Primary Artifact
The model is not documentation. It is an executable specification. The system is the execution of the model.
Controlled Extension
Custom behavior can be attached at defined extension points. Manual logic operates within the model-defined structure rather than replacing it.
Engineering Impact
Development effort shifts from writing code to defining behavior. Complexity moves from implementation volume to model clarity.
Why This Changes Development
Traditional development is code-first and structure emerges over time. MySirt is model-first: structure is defined upfront and logic is formalized. This shifts development from incremental coding to structural execution.