FlowOS transition types and inscription language documentation
From One Sentence to Live Deploy in 2:44 I dropped a single sentence into a Petri-net inbox at 15:48:56 UTC. By 15:51:40, a lime-green banner with the exact text I asked for was rendering on a public production site. No
Govern your agents before they govern you. Prompt-based agents are great until you put them anywhere near production. The context resets, the permissions are hand-waved, the tool calls are unauditable, the state lives in a chat transcript that nobody can
The Review-Fix-Test Pipeline — Three Agentic-Nets That Autonomously Audit, Repair, and Validate Your Codebase What if you could drop a single sentence like “review error handling across the system” into a place, walk away, and come back to find code
Agent transitions represent the most powerful building block in AgetnticOS. Unlike LLM transitions that process prompts and return responses, Agent transitions execute autonomous AI agents that can make decisions, call tools, and produce entirely new data structures. Key Innovation: Agent transitions have optional presets (agents … …
LLM (Large Language Model) transitions bring the power of AI directly into your agentic processes. They enable natural language processing, text generation, sentiment analysis, entity extraction, and intelligent routing – all orchestrated through simple inscriptions. Key Innovation: LLM transitions use a two-field emit pattern where … …
Command transitions execute shell commands and filesystem operations via the agentic-net-executor service. They enable your Petri nets to interact with the operating system – running scripts, managing files, invoking CLI tools, and integrating with external processes. Command transitions dispatch work to the executor service and … …
Template interpolation is how AgetnticOS transitions access and transform token data. Using ${…} syntax, you can reference input token fields, metadata, and build dynamic outputs in Map templates, HTTP bodies, LLM prompts, and more. Templates use hierarchical paths to access token data and metadata: Understanding … …
HTTP transitions connect your agentic processes to the outside world. They make REST API calls, process responses, handle authentication, implement retry logic, and route results based on HTTP status codes or response content. HTTP transitions call external APIs and emit parsed response data to success … …
ArcQL (Arc Query Language) is AgetnticOS’s query language for selecting tokens from places. Every transition preset uses ArcQL to specify which tokens to consume, making it fundamental to understanding how tokens agentic through your Petri nets. Key Rule: All paths must start with $ (the … …
The Pass transition is the foundational routing primitive in AgetnticOS Petri nets. It examines token data and decides where each token should go – without transforming it, without calling external systems, without side effects. Think of it as a railway switch operator: tokens arrive, get … …
