لم تُترجم هذه الصفحة بعد.

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.

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.

Agent

Anything that follows an instruction. The word is used in five ways:

  1. An AI agent in general: a program that uses an AI model to do work, and follows your instruction while it does.
  2. A coding agent: an AI tool that works on code in a project's folder, such as Claude Code, Codex or Cursor.
  3. 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.
  4. A deployed agent: one agent that your organization runs for one instruction, on a machine it names, from the editor.
  5. 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.

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.

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.

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.

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.

Archive

Making an instruction read-only without deleting it. Agents keep following its published versions. You can unarchive it later.

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.

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.

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.

Comment

A note on part of an instruction's text, with replies. It is for people only and never reaches agents.

Contributor

A role that can read an instruction, suggest changes and comment. A Maintainer decides on each suggestion.

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.

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.

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.

Developer mode

A setting each person turns on for themselves. It shows technical details in the editor, such as raw syntax and addresses.

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.

E

Explore

The place to find templates and the instructions people made public, and to start your own from one.

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.

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.

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.

Follower

An agent or AI app that follows an instruction. The Agents card lists them, with the version each one has.

Fork

Your own copy of someone else's instruction. It remembers where it came from, so you can offer your 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.

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.

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.

L

Live

The one version agents get when they follow an instruction without naming a version. Publishing normally makes the new version live.

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.

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.

Maintainer

A role that can edit an instruction directly, accept or reject suggestions, publish versions and make one live.

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.

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.

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.

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.

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.

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.

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.

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.

Plan

What an organization may do and how much of it: Community, Pro, Team or Enterprise. The plan belongs to the organization.

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.

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.

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.

R

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.

Reader

A role that can read an instruction, its suggestions, its comments and its history, and change nothing.

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.

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.

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.

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.

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.

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.

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.

Suggestion

A change to a few words of the draft, marked in the text, that waits for a Maintainer to accept or reject it.

T

Template

An instruction made to start from. Using one makes your own copy, which doesn't change when the template does.

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.

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.

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.

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.

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.

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.

For developers: the developer glossary.

Last checked against the product:

Was this page helpful? Report a problem