Overview
What an agentic ecosystem is made of, and which part each product plays.
Agentic system: An agentic system lets work get done by models that decide some of their own steps, rather than by code that fixes every step in advance.
This reference maps the ecosystem around such systems: the parts below, each defined once in the industry's own words on its own card, the specifications that connect them, and the products, each read against those definitions.
The parts, from the model up
The industry's terms in reading order: each uses only the words defined before it.
- Model A model is what decides: the one thing every other layer of an agentic system is built from.
- Agent harness An agent harness turns a model into an agent, so that what the model decides is carried out in the world.
- Agent An agent is what you deal with when work gets done: it reads, acts and reports in the world where a model alone cannot.
- Agentic system An agentic system lets work get done by models that decide some of their own steps, rather than by code that fixes every step in advance.
- Session A session keeps one run of an agent together, its context, its record and its place, so the work can be followed and resumed.
- Subagent A subagent lets an agent hand part of its work to another agent under its control and take back the result.
- Skill A skill is a common way to extend any agent harness with knowledge and procedures, so the same capability works across harnesses and costs the agent little until it is needed.
- Execution environment An execution environment, or environment for short, sets the bounds of an agent's work: where its actions run, and what they can reach.
- Machine A machine is the computer, physical or virtual, that execution environments run on.
- Agent host An agent host lets sessions outlive, and be shared across, the windows used to see them.
- Client A client lets you see and drive a session wherever you are, without the session living there.
- Cross-session messaging Cross-session messaging lets one session tell another what it needs to know while both are running, such as a finding, a status or a decision, without anyone copying it across.
- Agent team An agent team lets several agents take on one piece of work together, each working its own part and sharing and challenging what the others find, where one session would work through it alone.
- Remote agent A remote agent lets an agent use another system's agent as a service, asking it for work and getting results back without knowing or controlling how that system works.
- Tool A tool lets an agent act on the world, or fetch what it does not know, beyond what the model can do with its own text.
- Instruction file An instruction file gives every session in a place the same standing instructions, so they need not be repeated in each prompt.
- Plugin A plugin lets a whole working setup for an agent harness be installed, and shared, in one step, rather than gathered a piece at a time.
- Channel A channel lets something outside an agent's session reach it while it runs, so the agent can react to events that happen while nobody is watching.
The parts products play
Each product card names the terms the product is an instance of, so one product may appear under several. The word for these parts is still under review.
Agent harness
An agent harness turns a model into an agent, so that what the model decides is carried out in the world.
Agent
An agent is what you deal with when work gets done: it reads, acts and reports in the world where a model alone cannot.
Agent host
An agent host lets sessions outlive, and be shared across, the windows used to see them.
Knowledge Islands' own words
Words of the Knowledge Islands system, each mapped onto the industry's terms, among them the actor and the bot: a durable, named agent with its own memory and processes.
- Guild
A guild lets a session find the skills it needs among many, by grouping those that belong together and work together under one purpose a reader can name.
- Rig
A rig lets Knowledge Islands set up a machine, and put it right, the same way every time, so a session knows what it will find there.
- Actor
An actor gives each piece of work someone who answers for it, who stays the same while the sessions that act for it come and go.
- Work package
A work package gives one piece of work a single place where its scope, its changes and where they stand are kept, so whoever picks it up knows where things are.
- Backpack
A backpack lets a territory carry everything its agents need to work its way, and install it on any rig in one step.
- Role
A role says what a job owns and what it never does, so whoever takes a place in a piece of work knows its bounds before acting.
- Seat
A seat gives each job in a piece of work an address of its own, so work can be routed to it whoever holds it.
- Bot Draft
A bot gives an actor a home of its own on an agent host, so it can be reached by name and woken by messages and schedules without anyone opening a session for it, while the work it does stays on the record every actor shares.