AIGM / TECHNICAL REFERENCE

AIGMos.Runtime made explicit.

AIGMos is an actively developed command-surface runtime for structured AI and automation. It provides a concrete technical reference for visible state, explicit execution and inspectable human–AI interaction.

Technical referenceActive developmentLocal-first direction
AIGM ≠ AIGMos

AIGM is the standard. AIGMos is an implementation.

AIGM defines implementation-neutral principles and applicable requirements. AIGMos illustrates one possible runtime architecture; adopting it is not a condition of following the standard. The two have separate scopes and sources of authority.

Runtime architecture

Explicit components make behavior observable and command chains reproducible.

Operational loop

Input signals modify or inform state; triggers and events select command execution. Output can generate new signals.

  1. 01Signals
  2. 02State
  3. 03Triggers
  4. 04Events
  5. 05Execution
  6. 06Output

AIGMos also uses % runners for command workflows. The six-step loop summarizes observable behavior; it does not replace the separate runner abstraction.

Canonical primitives

Data symbols and runtime objects have distinct semantics. Their ownership boundaries must remain explicit.

Data / state

  • $Key/value state
  • #Structured namespace and tree state
  • &Ordered indexed list state

Runtime objects

  • !Trigger: passive condition or pulse
  • @Event: dispatches one command
  • %Runner: commands and bounded workflows
  • |Layout instance and its runtime state

Command Surface

The Command Surface provides a common interface for operating on state, runtime instances and execution. Triggers, events and runners are separate mechanisms; a runner is not a trigger and an event is not a script.

Current implementation areas

The working repository documents the following implemented components. Their presence does not imply production certification or readiness.

01 /

Command surface

Command parser and explicit dispatch instead of hidden control paths.

02 /

State and persistence

State primitives, storage backends and inspectable runtime ownership.

03 /

Triggers, events, runners

Separate condition detection, command dispatch and workflow execution.

04 /

Layout instances

Terminal-first instances such as |CS and |Q with instance-owned state.

05 /

LLM command forms

Stateful q and stateless qc commands for model-facing operations.

06 /

Extension points

Adapters and hooks for commands, inputs, roles and layouts.

Command example

A small extract of the current runtime syntax. For executable semantics, consult the repository and its current specifications.

mk $notes
set $notes:title AIGMos
cat $notes:title

new |Q /q

trig !ready $SYSTEM:mode == run
on !ready @start "run %main &boot"

Syntax examples illustrate separate state, layout and runtime controls. They do not represent a complete runnable application.

Implementation boundaries

A technical reference must also state what it does not guarantee.

01 /

Not a mandatory platform

AIGM does not mandate AIGMos, Python, a particular database or any specific user interface.

02 /

Development status

The runtime and contracts are evolving. Some historic documentation may not match current code; use the current code and locked rules as reference.

03 /

Licensing

The runtime repository declares a Business Source License. Review the actual license file before use or redistribution.

Primary references

The technical description is derived from the active repositories and is deliberately separate from normative AIGM definitions.