@orlan-maker/cli 0.5.0 → 0.12.0

package/dist/http.js

@@ -26,7 +26,7 @@ const explained = {
     login_used: "This sign-in code was already used. Run `orlan auth login` again.",
     login_rate_limited: "Too many sign-ins from this computer in a short time. Wait 10 minutes, then try again.",
     agent_scope_exceeded: "The agent asks for more than the person approved for this CLI: a topic or a role outside the approval. orlan connect can only narrow the access.",
-    pair_invalid: "Orlan does not know this --pair id. Copy the prompt again from the Connect dialog.",
+    pair_invalid: "This Orlan server does not know this --pair id. The id works only on the server of the Connect dialog: check --server, or copy the prompt again from the Connect dialog.",
     pair_expired: "The --pair id expired. It works for 10 minutes. Copy the prompt again from the Connect dialog.",
     pair_used: "Another CLI used this --pair id already. It works for one sign-in. Copy the prompt again from the Connect dialog.",
     org_suspended: "This organisation is suspended.",
@@ -49,7 +49,7 @@ const nextSteps = {
     login_used: "orlan auth login",
     login_rate_limited: "wait 10 minutes, then orlan auth login",
     agent_scope_exceeded: "ask your person to approve the access in Orlan: they run orlan auth login and include the topic there",
-    pair_invalid: "copy the prompt again from the Connect dialog in Orlan, or run orlan auth login",
+    pair_invalid: "run the prompt again with --server set to the address of the Orlan page that showed the Connect dialog",
     pair_expired: "copy the prompt again from the Connect dialog in Orlan, or run orlan auth login",
     pair_used: "copy the prompt again from the Connect dialog in Orlan, or run orlan auth login",
     org_suspended: "ask an admin of the organisation to contact Orlan",
@@ -78,6 +78,7 @@ const nextSteps = {
     task_invalid: "check the text, the topic, --thread and --assignee: `orlan tasks add --help`",
     decision_invalid: "check the title, the topic and --thread: `orlan decisions add --help`",
     plan_limit_agents: "orlan disconnect --agent <id>, or ask an admin to move the organisation to Team",
+    plan_limit_topics: "tell your person that an admin can move the organisation to Team (the link above), or add --topic <topic>",
     guest_account_agent_limit: "orlan disconnect --agent <id>, or add your email in Orlan",
     guest_account_file_limit: "add your email in Orlan (the bar at the top)",
     internal_error: "run the command again; when it fails again, tell your person",
@@ -238,9 +239,16 @@ export class AgentApi {
     post(pathname, what) {
         return this.send(this.url(pathname, {}), { method: "POST" }, what);
     }
-    /** POST a local file as the raw body of an agent route, with its query. */
+    /**
+     * POST a local file as the raw body of an agent route, with its query. The body is a file Blob
+     * (openAsBlob): it streams from the disk, so a large video is never all in memory (F133).
+     */
     postFile(pathname, query, body, what) {
-        return this.send(this.url(pathname, query), { method: "POST", headers: { "content-type": "application/octet-stream" }, body: new Uint8Array(body) }, what);
+        return this.send(this.url(pathname, query), { method: "POST", headers: { "content-type": "application/octet-stream" }, body }, what);
+    }
+    /** POST a multipart form to an agent route, with its query: a brand kit file (F141). */
+    postForm(pathname, query, body, what) {
+        return this.send(this.url(pathname, query), { method: "POST", body }, what);
     }
     /**
      * Sends a local file in one request and returns its upload id, for post or respond. The

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@orlan-maker/cli",
-  "version": "0.5.0",
+  "version": "0.12.0",
   "description": "The orlan command: connect Claude Code, Codex, Cursor or OpenCode to Orlan with a token and skills, and work with its topics, files and comments from the terminal.",
   "license": "MIT",
   "type": "module",
@@ -11,7 +11,8 @@
     "dist",
     "skills",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "THIRD_PARTY_NOTICES.md"
   ],
   "engines": {
     "node": ">=22.18"

package/skills/orlan/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: orlan
-description: Orlan is connected: the shared board of the person's team and its agents; the person connected you. Use it first, before any other diagram skill, for a diagram, a flowchart, an architecture or a map of a system. Also use it, without being asked to draw, when the person asks you to explain, compare or design a system, a flow or a process with parts and links ("explain how a CDN works"): answer in the chat and draw it on the board too. When the person asks to put an explanation, a plan, a guide or a summary in Orlan, build it on the board as a diagram and short notes, not as an HTML file. On Orlan a diagram is shapes and labeled arrows, not an HTML, SVG or image file. Also use it when the person says the canvas, the board, the topic, "in Orlan" or "on Orlan", asks what is on the board, asks for a page, deck, mock or file to review, or names a comment, a version or a request on Orlan. Do not use it for a short fact answer, a sum, a question on code, or a fix in a local file that the person names.
+description: Orlan is connected: the shared board of the person's team and its agents; the person connected you. Use it first, before any other diagram skill, for a diagram, a flowchart, an architecture or a map of a system. Also use it, without being asked to draw, when the person asks you to explain, compare or design a system, a flow or a process with parts and links ("explain how a CDN works"): answer in the chat and draw it on the board too. When the person asks to put an explanation, a plan, a guide or a summary in Orlan, build it on the board in frames, not as an HTML file. On Orlan a diagram is shapes and labeled arrows, not an HTML, SVG or image file. Also use it when the person says the canvas, the board, the topic, "in Orlan" or "on Orlan", asks what is on the board, asks for a page, deck, mock or file to review, or names a comment, a version or a request on Orlan. Do not use it for a short fact answer, a sum, a question on code, or a fix in a local file that the person names.
 ---
 
 # Orlan
 
 Orlan is one board for a team and its AI agents. A person opens a topic. The topic's board holds
-files (HTML, PDF, PowerPoint, images) as page tiles, and notes, text, frames and arrows. People
-comment on regions of pages, vote and set tasks. You work on the same board: you read it, post
-files and versions, reply to comments and resolve them.
+files (HTML, PDF, PowerPoint, images) as page tiles, MP4 and WebM videos as players, and notes,
+text, frames and arrows. People comment on regions of pages, vote and set tasks. You work on the
+same board: you read it, post files and versions, reply to comments and resolve them.
 
 `orlan connect` installs this skill, so Orlan is connected in this session. Do not ask the person
 if they mean Orlan.
@@ -29,18 +29,26 @@ task: it names the topic ("You are in "startups" (open in Orlan now)"), and ever
 topic, use `--topic <topic>`. When the brief says the person's open topic is out of your reach, tell
 the person, with the step the brief gives, before you work in another topic.
 
+When no topic is open, and you used none in the last minutes, Orlan makes a new topic for new work.
+Do not ask the person to open or make one. Give each command that adds to the board or posts a file
+`--new-topic "<subject>"`: a short name of the subject, for example `--new-topic "CDN explanation"`.
+Orlan uses it only when there is no topic, so it is safe to add every time. The command prints the
+new topic's name and link: give both to the person. When Orlan refuses (your role, the Free plan's
+topic limit, or an agent with a topic list), tell the person the reason and the link it gives.
+
 ## When to use Orlan
 
 - The person asks what is on the canvas or the board: run `orlan board` (every item with its id and
   place, the timer, the vote and the open tasks), read the files you need
   (`orlan files pull <file> --out <path>`), and answer from them.
 - The person asks for a diagram, a chart of a flow, a map of a system or a sketch: draw it on the board
-  with shapes and labeled arrows. Follow "Draw a diagram" below.
+  with shapes and labeled arrows. Follow "Explain on the board" below.
 - The person asks you to explain, compare or design a system, an architecture, a flow or a process, and
   the answer has parts and links between them ("explain how a CDN works", "monolith vs microservices",
   "design a payment flow"): answer in the chat, and also draw it on the board. Do not ask first, and do
-  not wait for the word "Orlan" or "board". End the answer with one line that says where the drawing
-  is: the topic and the frame. A short fact answer ("what port does HTTPS use") stays in the chat.
+  not wait for the word "Orlan" or "board". Follow "Explain on the board" below. End the answer with one
+  line that says where the drawing is: the topic and the frames. A short fact answer ("what port does
+  HTTPS use") stays in the chat.
 - The person asks you to put an explanation, a plan, a guide or a summary in Orlan ("put all of this in
   Orlan", "put it on the board"): build it on the board. Follow "Put it in Orlan" below. No HTML file.
 - The person asks for a note, a text, a shape, a frame or an arrow on the board: `orlan board add`.
@@ -54,80 +62,49 @@ the person, with the step the brief gives, before you work in another topic.
   a new version: `orlan files push <file> <path> --changelog "<what changed>"`.
 - A comment or a request names you: follow the `orlan-review` skill.
 
-## Put it in Orlan
+## Explain on the board
 
-"Put all of this in Orlan" after an explanation, a plan, a guide or a summary means: build it on the
-board, so that people get it at a glance. An HTML file is a tab that people must open; the board is
-what they see.
+The goal: explain it like I'm someone who knows nothing about this topic, with big pictures and few
+words, at the level the chat shows. Turn what you know into something the person understands in ten
+seconds. You pick the shape that fits the question: one frame or several, frames in frames, shapes,
+text, notes and labeled arrows, placed where you want, or a Mermaid flowchart. Ideas that help: draw
+the mechanism, not the name; one picture to hold, and where the picture breaks; real evidence the
+person can check, such as a header or a command and its output; the difference, drawn twice with the
+same layout. Look at the picture, and fix what a person would misread.
+
+A diagram on Orlan is board items: frames, shapes with words, text, notes and labeled arrows. An HTML,
+SVG or image file is a file on the board, not a drawing that people can change.
 
 1. `orlan brief` for the topic, and `orlan board` for a free place (right of or below the items).
-2. Cut the content into 2 to 5 parts. Each part gets one frame, with the part's name as its title, in
-   one row from left to right.
-3. The structure (steps, a flow, a decision, parts and their links) is a diagram in its own frame, drawn
-   as in "Draw a diagram".
-4. The key points are short notes in the frame of their part: one point in each note, at most 20 words,
-   3 to 6 notes in a frame. Make a frame and its notes in one `orlan board edit` step. A frame of
-   `40 + 210 * columns` by `80 + 140 * rows`, and each note (190 x 120) at
-   `20 + 210 * column`, `60 + 140 * row` from the frame's corner, with `"frame"` set to the frame's id:
-   `[{"op":"create","type":"frame","id":"money","x":0,"y":0,"w":460,"h":220,"text":"Money"},`
-   `{"op":"create","type":"note","x":20,"y":60,"text":"Keep 6 months of costs in the bank","frame":"money"},`
-   `{"op":"create","type":"note","x":230,"y":60,"text":"Pay yourself last","frame":"money"}]`
-5. Read the warnings and fix them. Look at it: `orlan board view --out <file.png>`, open the picture.
-6. End your answer with one line that names the topic and the frames: "I put it on the board of
-   "startups", in the frames "Basics", "Money" and "First steps"."
+2. Draw it in one step with `orlan board edit '<JSON>'`: give each new item an `"id"` of your own, so a
+   `"frame"` and the `"from"` and `"to"` of an arrow can name it. x and y are board points. A frame
+   holds the items you put in it, also another frame. For example:
+   `[{"op":"create","type":"frame","id":"hold","x":0,"y":0,"w":680,"h":420,"text":"1 · The picture to hold"},`
+   `{"op":"create","type":"text","id":"claim","x":30,"y":30,"text":"A CDN is a copy shop on your street.","size":"L","frame":"hold"},`
+   `{"op":"create","type":"shape","id":"you","kind":"ellipse","color":"yellow","x":40,"y":260,"text":"You","frame":"hold"},`
+   `{"op":"create","type":"shape","id":"shop","kind":"rounded","color":"blue","x":330,"y":250,"text":"Copy shop","frame":"hold"},`
+   `{"op":"create","type":"arrow","from":"you","to":"shop","text":"asks"}]`
+3. A flowchart can also come from Mermaid: `orlan board add frame "<title>" --id <frame> --at <x,y>`,
+   then `orlan board mermaid <file.mmd> --frame <frame>`. Drawing the file again replaces it.
+4. Read the warnings in the answer, and fix them with `orlan board edit` or `orlan board change`.
+5. Look at it: `orlan board view --out <file.png> [--frame <frame>]`, open the picture, and fix what a
+   person would misread.
+6. Tell the person what is on the board in one line after your answer: the topic and the frames. For a
+   new topic, also give its link.
+
+The goal comes from the eli5, visual-explainer and feynman-technique skills, with thanks. Their
+licences are in THIRD_PARTY_NOTICES.md of the orlan package.
+
+## Put it in Orlan
+
+"Put all of this in Orlan" after an explanation, a plan, a guide or a summary means: build it on the
+board, as in "Explain on the board", in the topic the brief names. An HTML file is a tab that people
+must open; the board is what they see.
 
 Do not post an HTML file or a document for this. Post a file only when the person asks for a page, a
 document, a deck or a mock, or when the content is long prose that people read as a document. Never
 make both a board version and a file, unless the person asks for both.
 
-## Draw a diagram
-
-A diagram on Orlan is board shapes with words and labeled arrows. Do not post an HTML file or notes as a
-diagram, do not use notes as boxes, and do not use another diagram skill or tool for it.
-
-1. Plan it: 5 to 15 boxes with 1 to 5 words each, and a label on each arrow that says what goes along
-   it ("sends JSON", "yes").
-2. A flow, a process, an architecture or a decision tree: write a Mermaid flowchart to a local file,
-   make a frame at a free place (right of or below the items `orlan board` shows), and draw it in the frame:
-   `orlan board add frame "<title>" --id <frame> --at <x,y>`, then
-   `orlan board mermaid <file.mmd> --frame <frame>`. Use `subgraph` for the groups, a diamond `{...}`
-   for a decision, a cylinder `[(...)]` for data. The frame fits the diagram.
-3. One picture is ONE Mermaid file and one import, also when it has several parts (a comparison,
-   variants, before and after, layers): one `subgraph` for each part, with no links between the parts.
-   `flowchart LR` stacks the parts as rows, `flowchart TB` puts them side by side; Orlan lines them up
-   in the order of the file. A key or a compare box is shapes in a subgraph of its own (`a ~~~ b` puts
-   two boxes side by side with no arrow), not a text item. All words keep one size.
-   A login, a payment or another exchange of messages between parties: one box for each step, in
-   order, that says who does what ("App sends the code to the auth server"), with a subgraph for each
-   phase. Do not draw each party once with arrows back and forth: the lines cross and the order is lost.
-4. Do not move, resize or add items by hand after the import. To change the picture, change the file
-   and run the same command again: it replaces your old version and fits the frame again.
-5. Another diagram (a grid, a layout, a timeline): `orlan board edit '<JSON>'` with the shapes, the
-   arrows and their labels in one step, each with an id of your own.
-6. Read the warnings in the answer. Fix each one in the file (change `LR` to `TB`, make the boxes
-   fewer) and draw again, until the answer has no warning.
-7. Look at it: `orlan board view --out <file.png> --frame <frame>`, open the picture, and fix words that
-   are cut, boxes that touch and arrows that are hard to follow.
-8. Tell the person what is on the board (the topic, the frame) in one line after your answer.
-
-Example for "monolith vs microservices", in `compare.mmd`:
-
-```
-flowchart LR
-  subgraph mono [Monolith]
-    u1[Users] -->|HTTPS| app1[One app] -->|SQL| db1[(One database)]
-  end
-  subgraph micro [Microservices]
-    u2[Users] -->|HTTPS| gw[API gateway] -->|REST| orders[Order service] -->|SQL| db2[(Orders DB)]
-  end
-  subgraph key [Compare]
-    k1[Monolith: simple to run] ~~~ k2[Microservices: scale each part]
-  end
-```
-
-Then `orlan board add frame "Monolith vs microservices" --id compare --at <x,y>`,
-`orlan board mermaid compare.mmd --frame compare` and `orlan board view --out compare.png --frame compare`.
-
 ## When not to use Orlan
 
 Do not call Orlan for work that has no link to the board: a sum, a short fact answer, a question on
@@ -182,6 +159,19 @@ show it, and every other command fails with `agent_stopped`. When you see it:
 - `orlan tasks add "<text>"` and `orlan tasks change <task id> --done` - the topic's tasks.
 - `orlan decisions add "<title>" --body "<text>"` - records a decision the people made.
 - `orlan search "<words>"` - finds topic and file names, page text, comments and decisions.
+- `orlan brand [--save <folder>]` - the accepted brand kit of the organisation: colors, fonts, logos, tone,
+  do and do-not rules, formats and references. Run it before you make a deck, a video, a carousel or a page,
+  and use the kit with no brand words in the prompt. `--save` writes the logo and font files. Use only what
+  it prints: a draft section waits for review, so do not guess it.
+- `orlan brand draft <section> --file <path> --note "<source>"` - when the person asks you to make the brand
+  kit: read the website, the logos and the files they give you, upload logo and font files with
+  `orlan brand upload <path> --kind logo|font`, then write each section. Each section is a draft until a
+  person accepts it; you cannot accept one. A person's request on a section ("Ask the agent") shows in
+  `orlan inbox` and `orlan brand`: answer it with `orlan brand draft <section> --request <id>`.
+- `orlan studio <skill> <step>` - one step of a studio skill (a video, a deck, a carousel, a walkthrough).
+  When the person asks you to make one, read the brand kit, then `orlan studio` for the skills, then
+  `orlan studio pull <skill>` for its helper scripts, then each step in order: brief, script, build,
+  render, review. Read each step when you come to it, and follow it.
 
 Run `orlan <command> --help` for the options of a command.
 
@@ -189,16 +179,15 @@ Run `orlan <command> --help` for the options of a command.
 
 - "what is in the canvas?" - run `orlan brief`, pull the files, and say what the board holds: the topic,
   each file and what it shows, and the open comments.
-- "create a diagram showing how to make a full stack app" - draw it in a frame with
-  `orlan board mermaid`, as in "Draw a diagram", check the warnings and the picture, and say what is on
-  the board. No HTML file, no notes.
-- "explain how a CDN works" - explain it in the chat, draw the parts and their links in a frame as in
-  "Draw a diagram", and end with one line: "I drew it on the board of <topic>, in the frame <title>."
-- "put all of this in Orlan", after you explained how to start a company - follow "Put it in Orlan":
-  a frame for each part, a diagram of the steps, short notes for the key points, in the topic the brief
-  names. No HTML file. End with the topic and the frames.
-- "put the notes on the board" - add them as short notes in a frame, as in "Put it in Orlan", at a free
-  place that `orlan board` shows.
+- "create a diagram showing how to make a full stack app" - draw it on the board as in "Explain on the
+  board", check the warnings and the picture, and say what is on the board. No HTML file.
+- "explain how a CDN works" - explain it in the chat, and on the board in the shape you pick, as in
+  "Explain on the board". End with one line: "It is on the board of <topic>, in the frames <titles>."
+  With no topic open, add `--new-topic "CDN explanation"` to the first command, and end with the new
+  topic's name and link.
+- "put all of this in Orlan", after you explained how to start a company - follow "Put it in Orlan", in
+  the topic the brief names. No HTML file. End with the topic and the frames.
+- "put the notes on the board" - add them as notes at a free place that `orlan board` shows.
 - "make a one-page HTML guide of this for the team" - the person asks for a page: make the file and
   post it with `orlan files add <path>`. No board version.
 - "what is 17*23?" - answer 391. No Orlan call.

package/skills/orlan-review/SKILL.md

@@ -24,6 +24,9 @@ Orlan is). You read the comments, fix the file, post a new version, reply, and r
 - `orlan comment <thread> "<text>"` - replies to a thread: `#12` or the thread id. To ask a person or
   point at a problem, open a thread: `orlan comment --file <file> --page <n> [--region <x,y,w,h>] "<text>"` on a page (region as
   fractions of the page), or `orlan comment --at <x,y> "<text>"` on the board. "@" and a name tells that person.
+  On a video: `--file <file> --time 0:42` (a time), `--time 0:40-0:48` (a range), `--time 0:42 --box <x,y,w,h>`
+  (a box on that frame) or `--scene <n>` (a scene of its shot list, from 1). A thread on a video names
+  its time, box or scene the same way.
 - `orlan comments resolve <thread>` - resolves a thread. When two topics have a `#12`, add `--topic`.
 - `orlan inbox` - prints your open requests: a mention of you in a comment, or an answer in a thread
   you asked in. `orlan inbox done <request id>` closes one when its work is done.
@@ -50,7 +53,8 @@ Add `--json` to a command for small JSON with a `next_step` field. An error says
 ## Work loop
 
 1. `orlan comments list --topic <topic>`.
-2. Pull the file, fix what each comment asks, and push one new version with a changelog.
+2. Pull the file, fix what each comment asks, and push one new version with a changelog. Name the
+   comments it answers with `--answers` (for example `--answers 3,5`): each shows "Answered in v<n>".
 3. Reply to each thread you answered: say what you changed and in which version.
 4. Resolve a thread only when your version fixes it. When you cannot fix it, reply with your question
    and leave it open, then end your turn: the answer comes to `orlan inbox` as a request. Never take a

package/skills/orlan-versions/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: orlan-versions
-description: Get a file from Orlan and post a new version of it with a changelog. Use when you must read, fix or replace a PowerPoint, PDF, image or HTML file in an Orlan topic.
+description: Get a file from Orlan and post a new version of it with a changelog. Use when you must read, fix or replace a PowerPoint, PDF, image, HTML or video file in an Orlan topic.
 ---
 
 # Orlan versions
@@ -23,6 +23,27 @@ description: Get a file from Orlan and post a new version of it with a changelog
 - `orlan files add <path>` - posts a local file as a new file on your topic and puts it on the board.
   `--topic <topic>` names the topic; the default is the topic the person has open in Orlan. `--at <x,y>` puts it at
   that point of the board (`orlan board` shows where the items are).
+- `orlan files add slide-*.png --carousel [--name "Launch carousel"]` - posts PNG or JPG slides as one
+  carousel: one file on the board, the slides in the order of the numbers in their names. A slide is a
+  page: a comment on slide 3 has page 3. `orlan files push <file> slide-*.png --changelog "..."` posts
+  its next version.
+- `--shots <shots.json>` on `files add` or `files push` of a video - its shot list: a JSON array of
+  `{ "name": text, "start": seconds, "end": seconds }`, the scenes in order. The review shows it as the
+  scene list. Orlan refuses a bad list with `shots_invalid` and names the problem.
+- `--answers 3,5` on `files push` - the comments this version answers, by their numbers (`#3` in
+  `orlan comments list`). Each one shows "Answered in v<n>" to the reviewers. A `#3` in the changelog
+  counts too. Orlan refuses a number that is no comment on the file with `answers_invalid`.
+- `--scores <scores.json>` on `files add` or `files push` - the critic scorecard of the version: a JSON
+  array of 1 to 20 `{ "name": text, "score": 0 to 10, "note": text }`, for example the 8 scores of a
+  critic round. People see it read only in the review and in Compare, with the change from the version
+  before. Orlan refuses a bad scorecard with `scores_invalid` and names the problem. `orlan files list`
+  shows the total of the newest scored version; `orlan comments list` shows "answered in v<n>".
+- `--source hf` on `files add` or `files push` of a video - its source folder (the hf/ folder of the
+  video skill). Orlan keeps it with the version. A person changes its fields (scene text, images, colors,
+  scene lengths) with Quick edit in Orlan. That saves a new source, and a comment asks you to render it.
+  Orlan refuses a source with GSAP code with `source_invalid`.
+- `orlan files source <file> [--out hf]` - saves the newest source of a video into the folder. When it
+  waits for a render, render it and push the mp4 with `--source hf` as the next version.
 - `orlan files rollback <file> --version 3 --changelog "<why>"` - posts an older version again, as the
   newest version. It waits for a person to make it current, as a push does.
 - `<file>` is the file id or the file name, and `<topic>` the topic id or its name. When a name is on two
@@ -31,6 +52,10 @@ description: Get a file from Orlan and post a new version of it with a changelog
 ## Rules
 
 - Write a changelog a reviewer understands: what changed and which comments it answers
-  (for example "Slide 3: homes connected added, as asked in #3").
+  (for example "Slide 3: homes connected added, as asked in #3"). Name the same comments with
+  `--answers 3`, so each one shows that this version answers it.
+- After a critic round, push its scorecard with the version (`--scores`).
 - Your version waits for a person to make it current. Tell the person that it waits.
+- Only a person finalizes a version (an admin or an editor presses Finalize in Orlan). You cannot: Orlan
+  refuses with `agent_cannot_finalize`. `orlan files list` shows the final version and its formats.
 - Pull with `--edit` before you change a file. Never force a post over another agent's version.