Glossary
This page is for anyone who meets a word they don't know in instruction.md. Each word has its plain meaning, the label the editor shows for it, the word developers use for the same thing, and the page that explains it.
The words developers use are there so you can follow a conversation with them, or read the developer docs. You never need them in the editor.
A
Activity log
The record of what happened in an organization: who changed, published, shared or read what, and when. It never holds the text of an instruction.
- In the editor: Activity
- Developers say: audit log
- Read more: See who did what
Admin
Two roles share this word. On an instruction or in a workspace, an Admin can do everything a Maintainer can, and also share it, decide who has access, rename, archive and delete it. In an organization, an admin runs the team: its people, workspaces, plan and rules.
- In the editor: Admin
- Developers say: manage (on an instruction); admin (in an organization)
- Read more: Invite people and choose their roles
Agent
Anything that follows an instruction. The word is used in five ways:
- An AI agent in general: a program that uses an AI model to do work, and follows your instruction while it does.
- A coding agent: an AI tool that works on code in a project's folder, such as Claude Code, Codex or Cursor.
- An agent in your organization: an agent with a sign-in of its own, a member of your organization with the role you give it, at most Maintainer. It never takes a seat.
- A deployed agent: one agent that your organization runs for one instruction, on a machine it names, from the editor.
- The places named after them: the Agents card on an instruction, which lists what follows it, and the Agents app, where you talk with your deployed agents.
- Developers say: agent, host, consumer, deployment (depending on the meaning)
- Read more: How instruction.md works: Following
Agent credential
The sign-in of an agent that works on its own, without a person. An organization admin makes it, and the agent then joins the organization as a member with an Agent badge.
- In the editor: API keys
- Developers say: agent credential (API key)
- Read more: Agents in your organization
Agents app
The page at instruction.md/agents where you see the agents your organization runs, answer what they ask, and write to them, on a computer or a phone.
- In the editor: Agents
- Read more: The Agents app
Agents card
The card on an instruction that lists the agents and AI apps following it, the version each one has, and whether it is behind.
- In the editor: Agents
- Developers say: bindings and consumers
- Read more: See which agents follow an instruction
AI app
An AI chat or tool you connect to instruction.md as yourself, such as Claude or ChatGPT. It acts as you, with your role, and asks you before it publishes.
- In the editor: Connected apps
- Developers say: host, MCP client
- Read more: Connect Claude or ChatGPT
Archive
Making an instruction read-only without deleting it. Agents keep following its published versions. You can unarchive it later.
- In the editor: Archive
- Read more: Archive an instruction
Assistant
instruction.md's own AI helper in the editor. It answers questions about the open instruction and suggests changes, which you accept or reject. It never publishes.
- In the editor: Assistant
- Read more: The assistant
C
Checkpoint
An earlier copy of your draft that History keeps as you write. Only the people who work on the instruction see it. No agent reads it.
- In the editor: Checkpoint
- Developers say: checkpoint
- Read more: See history and compare versions
Coding agent
An AI tool that works on code in a project's folder, such as Claude Code, Codex, Cursor or GitHub Copilot CLI. A project can make it follow an instruction.
- Developers say: coding agent, host
- Read more: Make your team's coding agents follow an instruction
Comment
A note on part of an instruction's text, with replies. It is for people only and never reaches agents.
- In the editor: Comment
- Developers say: comment thread
- Read more: Suggest changes and review them
Contributor
A role that can read an instruction, suggest changes and comment. A Maintainer decides on each suggestion.
- In the editor: Contributor
- Developers say: suggest
- Read more: Invite people and choose their roles
D
Deployment
One agent that your organization runs for one instruction, on a machine you name. A deployment rule starts one for every instruction in a project or a folder.
- In the editor: Deploy to…, Run every instruction here on…
- Developers say: deployment, deployment rule
- Read more: Run your instructions as agents
Deployment rule
A rule on a project or a folder that runs every instruction in it as an agent, on a machine you name. A new instruction there gets its agent too.
- In the editor: Run every instruction here on…
- Developers say: deployment rule
- Read more: Run every instruction in a project or a folder
Details
The part at the top of an instruction that says what it is: its title, its version label and other settings. Agents don't receive it.
- In the editor: Details
- Developers say: front matter
- Read more: What an instruction can say
Developer mode
A setting each person turns on for themselves. It shows technical details in the editor, such as raw syntax and addresses.
- In the editor: Developer mode
- Read more: Developer mode for new members
Draft
The text of an instruction you are editing now. It is saved as you type, and shared by everyone who edits it. No agent reads it.
- In the editor: Draft
- Developers say: draft
- Read more: How versions work
E
Explore
The place to find templates and the instructions people made public, and to start your own from one.
- In the editor: Explore
- Read more: Explore: templates and public instructions
F
Folder
A way to group instructions inside a project. Folders can hold more folders. They help you find things and don't change who can read them.
- In the editor: Folder
- Read more: Group instructions in projects and folders
Follow
What an agent does with an instruction: it reads the version a name points to, and switches when the name moves. You choose the name it follows, such as latest or stable, or one exact version.
- In the editor: Follow in your coding agent…
- Developers say: binding (what is followed), consumer (who follows)
- Read more: How instruction.md works: Following
Follow file
A small file in a project's folder that says which instruction the project's coding agents follow, and at which version. The project shares it with its code, so everyone follows the same one.
- Developers say: the follow file
- Read more: Make your team's coding agents follow an instruction
Follower
An agent or AI app that follows an instruction. The Agents card lists them, with the version each one has.
- In the editor: Agents
- Developers say: consumer
- Read more: See which agents follow an instruction
Fork
Your own copy of someone else's instruction. It remembers where it came from, so you can offer your changes back.
- In the editor: Fork — a copy of your own
- Developers say: fork
- Read more: Copy an instruction and offer changes back
G
Guest
Someone in an organization who sees only what is shared with them, one instruction at a time. A guest takes no seat.
- In the editor: Guest
- Developers say: guest
- Read more: Invite people and choose their roles
H
History
The list of an instruction's checkpoints and published versions. From there you compare two of them, bring earlier text back into the draft, or make an older version live.
- In the editor: History
- Read more: See history and compare versions
I
Instruction
A document of rules and guidance for AI agents, written in the editor. Lines that start with a rule word such as MUST, SHOULD or NEVER are rules for the agent.
- In the editor: Instruction
- Developers say: instruction (a document in the first edition of the specification)
- Read more: What an instruction can say
Integration
A tool server, an API, a skill or an agent your organization adds, so writers can pick it by name while they type.
- In the editor: Integrations
- Developers say: integration
- Read more: Add the tools your agents may use
L
Live
The one version agents get when they follow an instruction without naming a version. Publishing normally makes the new version live.
- In the editor: Live
- Developers say: the version the default ref (latest) points to
- Read more: Roll back or withdraw a version
Live updates
Being told the moment a new version is published, instead of checking. Reading is never limited; on the Community plan, one agent or AI app at a time gets live updates.
- Developers say: subscriptions, events
- Read more: Reading and live updates
M
Machine
The computer, server or service where your organization's agents run. You give it a short name, such as laptop or support-server.
- In the editor: Where they run
- Developers say: platform
- Read more: Run your instructions as agents
Maintainer
A role that can edit an instruction directly, accept or reject suggestions, publish versions and make one live.
- In the editor: Maintainer
- Developers say: publish
- Read more: Invite people and choose their roles
Member
Someone in an organization who works on its instructions with the role they have in each workspace. A member takes a seat. The organization's other roles are owner, admin, billing and guest.
- In the editor: Member
- Developers say: member
- Read more: Roles in the organization
Mention
A name in an instruction that points at exactly one person, tool, skill, rule or parameter. You make one by typing @, &, # or $ and picking from the list. It shows as a chip.
- In the editor: @, &, #, $
- Developers say: reference
- Read more: Mention people, tools and other instructions
N
Notes
The part at the end of an instruction that keeps its record: authors, owners, review dates and sources. Agents don't receive it.
- In the editor: Notes
- Developers say: backmatter
- Read more: What an instruction can say
O
Offered changes
A whole new text you write in your fork and offer back to the original. A Maintainer of the original reviews and merges it as a new version.
- In the editor: Offer changes
- Developers say: proposal
- Read more: Copy an instruction and offer changes back
Organization
The team. It holds the plan and the bill, the seats, the people and their roles, the rules, the apps and keys, integrations, company sign-in and the assistant switch. Every account has a Personal one.
- In the editor: Organization
- Developers say: organization (org)
- Read more: Organizations and workspaces
Owner
The top role in an organization. An owner can do everything an admin can, and only an owner makes another owner or deletes the organization.
- In the editor: Owner
- Developers say: owner
- Read more: Roles in the organization
P
Parameter
A value an instruction leaves open, such as a refund limit, with a default. Whoever uses the instruction can set it without changing the text.
- In the editor: $
- Developers say: parameter
- Read more: Mention people, tools and other instructions
Passkey
How you sign in to instruction.md: your device's own way of unlocking, such as your fingerprint, your face or its PIN. There is no password.
- In the editor: Passkey
- Read more: Passkeys
Pin
Following one exact version, such as v4. A pinned agent stays on it until you choose another.
- In the editor: Only v4
- Developers say: a pinned version
- Read more: Pin to one version
Plan
What an organization may do and how much of it: Community, Pro, Team or Enterprise. The plan belongs to the organization.
- In the editor: Your plan
- Read more: Plans, limits and billing
Project
A group of instructions in a workspace, for example one per team or per agent. It can hold folders. A project or a folder can have a rule that runs every instruction in it as an agent.
- In the editor: Project
- Read more: Group instructions in projects and folders
Publish
Making a new version from the draft. Unless you publish quietly, it becomes the live version and the agents following latest switch to it.
- In the editor: Publish
- Developers say: release
- Read more: Publish, schedule and write a version message
Publish gates
The rules a version name keeps, such as taking signed versions only, or moving by itself to each new live version after a wait.
- In the editor: Publish gates…
- Developers say: ref policy, gates
- Read more: Publish gates
Q
Quiet version
A version you publish without making it live. It is kept and numbered, and agents stay on the version they have until you promote it.
- In the editor: Make it live — agents switch to it (unticked)
- Developers say: a version that moves no ref
- Read more: Make it live, or publish quietly
R
Read link
A link anyone can open, without an account, to read one version or whichever version a name points to, until it runs out or you revoke it.
- In the editor: Read links
- Developers say: read link
- Read more: Give read access with a link
Reader
A role that can read an instruction, its suggestions, its comments and its history, and change nothing.
- In the editor: Reader
- Developers say: read
- Read more: Invite people and choose their roles
Recovery code
One of a set of codes you get with your first passkey. Each one signs you in once if you can't use your passkey.
- In the editor: Recovery codes
- Read more: Recovery codes
Revoke
Marking one version as one no agent should use again. It can't be undone. The version stays in History, marked Revoked, and agents pinned to it keep their last good version.
- In the editor: Revoke…
- Developers say: revoke
- Read more: Revoke a version
Rule
A line of an instruction that starts with a rule word, so the agent knows it binds it. The rule words are MUST, MUST NOT or NEVER, SHOULD, SHOULD NOT or AVOID, MAY, ALWAYS and GUARDRAIL. BECAUSE gives the reason.
- In the editor: Rule
- Developers say: rule (a keyword line)
- Read more: What an instruction can say
Runner
The program someone starts on a machine once, with the command the editor gives. It starts your organization's agents there and keeps them in step with what you choose in the editor.
- Developers say: runner
- Read more: Run your instructions as agents
S
Sealed
Says who can read an instruction. A sealed workspace's instructions are encrypted on its people's devices, and only the people given its key can read them, not even instruction.md. Sealed workspaces are in beta, not yet independently reviewed.
- In the editor: Sealed
- Developers say: sealed (end-to-end encrypted)
- Read more: Sealed workspaces
Seat
A place for one person in a paid organization. Everyone except guests takes a seat. Agents don't.
- In the editor: Seats
- Read more: Plans, limits and billing
Signed
Says who published a version. Every version is signed for you with your organization's key, so an agent can check it came from your organization and wasn't changed.
- Developers say: signed release
- Read more: Signed and sealed
Stable
A version name you create yourself, which moves only when you move it or when its gates move it. Agents that follow stable don't switch on every publish. It doesn't exist until you create it.
- In the editor: stable
- Developers say: the stable ref
- Read more: Keep agents on a stable version
Suggestion
A change to a few words of the draft, marked in the text, that waits for a Maintainer to accept or reject it.
- In the editor: Suggestion
- Developers say: suggestion
- Read more: Suggest changes and review them
T
Template
An instruction made to start from. Using one makes your own copy, which doesn't change when the template does.
- Developers say: template
- Read more: Start from a template, a prompt or a file
V
Version
A copy of the draft you published: v1, then v2, and so on. A version never changes. It is not the version label you may write yourself in the Details, such as 2.1, which is for people only.
- In the editor: v1, v2…
- Developers say: version, release
- Read more: How versions work
Version label
A label you write yourself in the Details, such as 1.4. It is for people only. It doesn't change which version agents follow.
- Developers say: version label (the version: key)
- Read more: The version label and published versions
Version name
A name that points at one version and can move, such as latest or stable. Agents follow a name, so moving it changes what they get.
- In the editor: latest, stable
- Developers say: ref
- Read more: Keep agents on a stable version
Visibility
Who can read an instruction's published versions: Only you, Your organization, or Everyone (anyone, signed in or not). The draft is never public.
- In the editor: Only you, Your organization, Everyone
- Developers say: private, internal, public
- Read more: Who can read it
W
Workflow
Steps in a fixed order written into an instruction, drawn as a diagram, with points where a person must approve. It runs only in a program built to run workflows, never by itself.
- In the editor: Workflow
- Developers say: workflow
- Read more: Workflows, explained
Workspace
A place inside an organization that holds instructions, projects and folders. It is open (everyone in the organization sees it), restricted (only the people added) or sealed.
- In the editor: Workspace
- Developers say: workspace
- Read more: Organizations and workspaces
Words that are easy to mix up
| These words | The difference |
|---|---|
| Draft, checkpoint, version | The draft is what you edit now. A checkpoint is an earlier copy of the draft, for you. A version is what you published, for agents. |
| Live, stable, pin | Live is the version agents get by default, and it moves when you publish. Stable moves only when you move it. A pin never moves. |
| Publish, release | The same act. People say publish; developers say release. |
| Signed, sealed | Signed says who published a version. Sealed says who can read it. |
| Organization, workspace | The organization is the team, with its plan and people. A workspace holds the instructions. |
| Suggestion, comment, offered changes | A suggestion changes a few words of the draft. A comment is a note. Offered changes are a whole text from your own copy. |
| AI app, coding agent, deployed agent | An AI app acts as you. A coding agent works in a project's folder. A deployed agent runs on your organization's machine for one instruction. |
How instruction.md works puts these words together into the whole picture.
Related
- How instruction.md works
- Questions and answers
- How versions work
- Invite people and choose their roles
- Something isn't working
For developers: the developer glossary.