attune-system/attune
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

working on runtime executions

Browse Source
This commit is contained in:
David Culbreth
2026-02-16 22:04:20 -06:00
parent f52320f889
commit 904ede04be
99 changed files with 6778 additions and 5929 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
reference/models.md
View File

@@ -52,27 +52,22 @@ Attune is an event-driven automation and orchestration platform with built-in mu
## Runtime Environment
### `RuntimeType` (Enum)
**Values**: `action`, `sensor`
**Purpose**: Distinguishes between action execution environments and sensor monitoring environments.
### `Runtime`
**Purpose**: Defines an execution environment for actions or sensors.
**Purpose**: Defines a unified execution environment for actions and sensors.
**Key Fields**:
- `ref`: Unique reference (format: `pack.(action|sensor).name`)
- `runtime_type`: Type of runtime (action or sensor)
- `name`: Runtime name (e.g., "python3.11", "nodejs20")
- `distributions`: JSON describing available distributions
- `ref`: Unique reference (format: `pack.name`, e.g., `core.python`, `core.shell`)
- `name`: Runtime name (e.g., "Python", "Shell", "Node.js")
- `distributions`: JSON describing available distributions and verification metadata
- `installation`: JSON describing installation requirements
- `execution_config`: JSON describing how to execute code (interpreter, environment setup, dependencies). Runtimes without an `execution_config` (e.g., `core.builtin`) cannot execute actions — the worker skips them.
- `pack`: Parent pack ID
**Relationships**:
- Belongs to: pack
- Used by: workers, sensors, actions
**Purpose**: Defines how to install and execute code (Python, Node.js, containers, etc.).
**Purpose**: Defines how to install and execute code (Python, Node.js, containers, etc.). Runtimes are shared between actions and sensors — there is no type distinction.
### `WorkerType` (Enum)
**Values**: `local`, `remote`, `container`
@@ -479,7 +474,7 @@ These ensure data consistency and provide audit trails throughout the system.
## Common Patterns
### Reference Format
Most components use a `ref` field with format `pack.name` (e.g., `slack.webhook_trigger`). Runtimes use `pack.(action|sensor).name`.
All components use a `ref` field with format `pack.name` (e.g., `slack.webhook_trigger`, `core.python`, `core.shell`).
### Ref vs ID
- Foreign key relationships use IDs