working on runtime executions

This commit is contained in:
2026-02-16 22:04:20 -06:00
parent f52320f889
commit 904ede04be
99 changed files with 6778 additions and 5929 deletions

View File

@@ -4,6 +4,8 @@
**Status:****COMPLETE AND TESTED**
**Enhancement:** Sensor Worker Registration
> **⚠️ Note:** This document was written before the `runtime_type` column was removed from the runtime table. SQL examples referencing `WHERE runtime_type = 'sensor'`, `INSERT ... runtime_type`, and 3-part refs like `core.sensor.python` are outdated. The current architecture uses unified runtimes with 2-part refs (`core.python`, `core.shell`) and determines executability by the presence of `execution_config`. See `docs/QUICKREF-unified-runtime-detection.md` for the current model.
---
## Overview

View File

@@ -3,6 +3,8 @@
**Version:** 1.0
**Last Updated:** 2026-02-02
> **⚠️ Note:** This document was written before the `runtime_type` column was removed from the runtime table. SQL examples referencing `WHERE runtime_type = 'sensor'`, `INSERT ... runtime_type`, and 3-part refs like `core.sensor.python` are outdated. The current architecture uses unified runtimes with 2-part refs (`core.python`, `core.shell`) and determines executability by the presence of `execution_config`. See `docs/QUICKREF-unified-runtime-detection.md` for the current model.
---
## Overview

View File

@@ -1,5 +1,7 @@
# Native Runtime Support
> **⚠️ Note:** This document was written before the `runtime_type` column was removed from the runtime table. SQL examples referencing `INSERT ... runtime_type` and 3-part refs like `core.action.native` / `core.sensor.native` are outdated. The current architecture uses unified runtimes with 2-part refs (`core.native`) and determines executability by the presence of `execution_config`. See `docs/QUICKREF-unified-runtime-detection.md` for the current model.
## Overview
The native runtime allows Attune to execute compiled binaries directly without requiring any language interpreter or shell wrapper. This is ideal for: