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

8
docs/packs/core-pack-integration.md
View File

@@ -3,6 +3,8 @@
**Last Updated**: 2026-01-20
**Status**: Implementation Guide
> **⚠️ Note:** This document was written during early planning. Some code examples reference the now-removed `runtime_type` field and old 3-part runtime ref format (`core.action.shell`). The current architecture uses unified runtimes with 2-part refs (`core.shell`) and determines executability by the presence of `execution_config`. See `docs/QUICKREF-unified-runtime-detection.md` for the current model.
---
## Overview
@@ -316,11 +318,11 @@ pub async fn execute_action(
// Prepare environment variables
let env = prepare_action_env(&params);
// Execute based on runner type
let output = match action.runtime_type.as_str() {
// Execute based on runtime name (resolved from runtime.name, lowercased)
let output = match runtime_name.as_str() {
"shell" => self.execute_shell_action(script_path, env).await?,
"python" => self.execute_python_action(script_path, env).await?,
_ => return Err(Error::UnsupportedRuntime(action.runtime_type.clone())),
_ => return Err(Error::UnsupportedRuntime(runtime_name.clone())),
};
Ok(output)

2
docs/sensors/SUMMARY-database-driven-detection.md
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

2
docs/sensors/database-driven-runtime-detection.md
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

2
docs/sensors/native-runtime.md
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: