Enterprise AI glossary
What an agent harness, workstream, write-back gate, and enterprise AI OS actually are — the nouns operators need before they buy.
Explainers
- Explainer
Agent Harness vs Agent Framework
An agent framework is a library for assembling a loop.
Read article - Explainer
Agents Should Be Disposable
The project survives the agent.
Read article - Explainer
How a loop differs from RPA
RPA records clicks on screens.
Read article - Explainer
How to Design Collaborative Canvas UX for Human-AI Teams
Visual design patterns, spatial interaction models, and human-in-the-loop review mechanisms for real-time multiplayer AI workspaces.
Read article - Explainer
Inner vs Outer Agent Harness
An inner agent harness runs a developer and a repository — CLAUDE.md, hooks, tests.
Read article - Explainer
Loop Engineering vs Harness Engineering
Harness engineering designs the runtime around a model.
Read article - Explainer
Loop vs Workflow vs Agent
A workflow enumerates steps a person invented.
Read article - Explainer
Multiplayer AI vs multi-agent AI: what is the difference?
Multiplayer AI is people and AI on one job.
Read article - Explainer
Real-Time Sync Protocols for AI: Managing State with CRDTs
How CRDTs handle continuous streaming LLM tokens and human edits in a single coherent document without race conditions.
Read article - Explainer
Solo AI versus Multiplayer AI
A personal assistant is not team software. Solo AI is one person and one chat. Multiplayer AI is a job more than one person can open — same brief, same files, same refusal.
Read article - Explainer
What is a Company Wiki for AI Agents
A company wiki for AI agents is the official playbook the AI must follow: versioned, owned, and scoped.
Read article - Explainer
What is a Lifecycle Graph
A lifecycle graph is how a company answers “why did this happen?” after AI is involved — the chain of cause and effect, not a chat log.
Read article - Explainer
What is Agentic MapReduce
Agentic MapReduce splits a wide search across agents, then merges one consistent result so the next similar query does not start from scratch.
Read article - Explainer
What is AI Governance
AI governance is the working rules for who may use which AI, on which data, and whether it may change a live business system.
Read article - Explainer
What is AI Token Economics
AI token economics treats model usage as a budget: you pay per chunk of text read and written, so finance can quote, cap, and attribute it.
Read article - Explainer
What is an Agent Harness
An agent harness is everything around a model that lets it do work: tools, memory, permissions, loops, and stops.
Read article - Explainer
What is an Agentic Workflow
An agentic workflow is a sequence of steps an AI can run toward a goal, with a person who must approve before a live system changes.
Read article - Explainer
What is an AI Workstream
An AI workstream is one shared job: a brief, the tools allowed, the people and AI on it, a budget, and a finish line.
Read article - Explainer
What is an Enterprise Agent Harness
An enterprise agent harness is the outer runtime for operators: a wiki, scoped connectors, agent teams, write gates, and a ledger.
Read article - Explainer
What is an Enterprise AI Operating System
An enterprise AI operating system is the layer between the AI model and how departments actually work — like Windows sits between the chip and your apps.
Read article - Explainer
What is Causal AI for Operations
Causal AI for operations answers why a change happened, using the actual steps and the approval, not a guess about the chatbot.
Read article - Explainer
What is Enterprise RAG
Enterprise RAG is looking up authorised company files before the AI answers, with permissions respected — lookup-then-answer, not an operating system.
Read article - Explainer
What is Harness Engineering
Harness engineering fixes the environment when an agent fails — tools, hooks, tests, and stops — instead of rewriting the prompt.
Read article - Explainer
What is Human-in-the-Loop AI
Human-in-the-loop AI means a person must approve the exact change before the AI can finish the job, and that approval is kept.
Read article - Explainer
What is Institutional Memory in Enterprise AI
Institutional memory is what the company still knows after the person who did the work leaves: playbooks, signed decisions, and live systems.
Read article - Explainer
What is Loop Engineering
Loop engineering compiles the known path for unattended work, detects when reality changes, and records what was skipped.
Read article - Explainer
What is Model Context Protocol
Model Context Protocol is a common plug so AI apps can use the same tools, like USB for accessories.
Read article - Explainer
What is Model Routing
Model routing uses a cheaper model for simple steps and a stronger model only when the task needs it.
Read article - Explainer
What is Multi-Agent AI
Multi-agent AI is more than one specialist handing work along, with a shared job and a person who must approve a live change.
Read article - Explainer
What is RBAC for enterprise AI, and why should you care?
A shared chatbot login is not access control when a model can see customer files — or write to a live system — under someone else’s credentials.
Read article - Explainer
What is Write-Back Governance
Write-back governance means an AI may not change a live system until a named person has seen the exact change and signed it.
Read article - Explainer
What shadow AI means at work
Shadow AI is people using personal chatbots for work because the official tool is too slow, which leaks data and leaves no record.
Read article
Architecture
- Architecture
Agent Harness Architecture
Agent harness architecture is the runtime around a model: the loop, tools, context, permissions, and the checks that decide when it must stop.
Read article - Architecture
Eval Loops for Enterprise Agent Harnesses
Coding agents can be scored on SWE-bench and Terminal-Bench.
Read article - Architecture
Governance as a Multiplayer Primitive
Governance belongs in the room — roster, inherited authority, spend as scheduling, notify the job not the org.
Read article - Architecture
The Four Pillars of an Enterprise AI Platform
An enterprise AI platform stands on Communication, Collaboration, Automate, and Governance, so teams finish work without personal-account workarounds.
Read article
Loops
- Architecture
A Loop Is Not an Agent
On the normal path a loop never invokes a model.
Read article - Explainer
Six Things That Start a Loop
A standing-order loop starts on a schedule, when a file lands, when data changes, when someone drops a file, when another system pings, or on demand.
Read article - Explainer
What is a Nimbus Loop
A Nimbus Loop is a standing order on a workstream: a trigger, a compiled recipe, and a run page, without turning the job into a chat ritual.
Read article
See what governed AI looks like on your stack.
Connect your tools, run a workstream, and keep every decision on your ledger. Start on Free.