Glossary

Short definitions. User-facing guides avoid most of these names; they still appear in architecture pages and plugin manifests.

---

Plugin SDK

Go module github.com/actonos/plugin-sdk plus the acton-plugin CLI. You use it to scaffold, build, test, sign, and pack WebAssembly plugins. Start at Plugin SDK overview.

acton-plugin

Developer CLI (new, validate, build, test, sign, pack). Current SDK version: 1.3.0.

WASMLoader

ActonOS subsystem that discovers, validates, starts, and hot-reloads WebAssembly plugins (tools, channels, connectors).

Wazero

Pure-Go WebAssembly engine inside actond. Plugins run here, not as native host processes.

.actonpkg

Zip package: manifest.json, plugin.wasm, optional signature.sig and README.md. Upload it on Plugins.

Tool / Channel / Connector

The three plugin capabilities. Tool = a function an agent calls. Channel = a chat app adapter. Connector = a SaaS integration whose actions can also become tools.

Hardware Abstraction Layer (HAL)

The system layer in ActonOS that detects whether the host is running directly on physical Bare-Metal hardware (x86_64 MiniPC) or inside a Docker container, transparently adapting network drivers, telemetry sensors, and sandbox executors.

Model Context Protocol (MCP)

An open standard introduced by Anthropic enabling AI models to interact securely with external tools, data sources, and servers via stdio and HTTP/SSE JSON-RPC protocols.

ReAct Loop (Reasoning + Acting)

An autonomous agent execution pattern where the LLM alternates between generating natural language reasoning thoughts and calling structured tools to observe real-world outputs before reaching a conclusion.

Swarm Orchestration

A multi-agent coordination pattern where a parent orchestrator agent decomposes a large goal into independent subtasks and delegates execution concurrently across specialized child agents using lightweight Go Goroutines.

Bubblewrap (bwrap)

An unprivileged sandboxing utility on Linux that creates lightweight isolated user, mount, PID, and network namespaces without requiring root permissions.

Cgroups v2 (Control Groups)

The Linux kernel mechanism used by ActonOS to strictly enforce maximum memory limits (e.g. 512 MB RAM), CPU bandwidth quotas, and process count ceilings on agent executions.

Hybrid Semantic Memory (RAG)

A dual-engine retrieval system combining SQLite FTS5 (for exact keyword/token matching with BM25) and dense vector embeddings (generated by local ONNX multilingual-e5-small) stored in chromem-go.

Ebbinghaus Cognitive Decay

A mathematical model (R = exp(-t / S)) applied during context retrieval to gradually decay older, unreferenced memories while keeping frequently recalled facts primed for LLM reasoning.

Embedded tsnet

The pure-Go Tailscale client embedded directly within the actond daemon, providing an encrypted WireGuard mesh connection and automatic HTTPS domain without requiring external VPN clients.

Self-Healing OTA Update

An atomic update mechanism that downloads new binaries to versioned release folders, swaps the /data/bin/actond symlink, and automatically rolls back to the previous version if a 30-second health check watchdog fails.

User Workspace

The documents you see on the Workspace page. Uploaded and saved files keep their original names (report.pdf). Agents read, write, and send these files with native_workspace_* tools. This is separate from the agent’s private scratchpad.

Named file view (user-workspace/)

A folder of original filenames that scripts and native_exec (Python, shell) can open. The environment variable ACTONOS_USER_WORKSPACE points here. You still work with names like report.pdf; you do not pass internal storage IDs to Python.

Agent scratchpad

A private working folder for temporary scripts and unfinished files. Those files are not listed on the Workspace page until the agent publishes them (for example with native_workspace_write).

Channel file send

When you ask an agent to send a workspace document to Telegram, Discord, Slack, WhatsApp, or Zalo, ActonOS loads the file and forwards the bytes to the installed channel plugin. The plugin uploads to that chat app. The core OS does not implement Telegram or Zalo upload APIs itself.