Tuning by demonstration

Added · Seed

A first draft. The forms listed are sightings sorted by eye, and the claim that the agent should state what it learned is taken from a few products that do.

… the actor wants an agent, or a tool such as a spreadsheet, to do something their way and cannot easily say what that way is: a tone, a route, a manner of handling a certain kind of case. Standing instructions need the preference in words, and rule composition needs it in the system's terms. The actor can do the thing, or can point to an instance of it done well.

Problem

Much of what people know about how they want work done they cannot put into words, and what they do put into words leaves out what seemed too obvious to say. An agent that can only be told is limited to what its actor can articulate.

Showing takes several forms, and delegation uses them both when an agent is set up and when it is corrected. The actor demonstrates on purpose: fills in two cells and lets the spreadsheet complete the column, or records the steps once. The actor points to an example: write like this sample, set this device up like the last one. Or the actor marks a limit in the world the agent works in, as with a barrier a robot will not cross.

A single demonstration rarely pins down one rule. When actors choose examples themselves, they pick typical cases and leave out edge cases, so several plausible generalisations fit what they showed. Rather than guessing silently, the system can test candidate interpretations against the remaining items and surface the distinguishing cases where those interpretations disagree.

Solution

Let the actor teach by showing: doing the task once while the agent observes, correcting the agent’s attempt by hand, or pointing to an example to follow. Say before a demonstration what the agent will attend to. Afterwards state in plain words what it took from the example, surface any cases where plausible interpretations disagree so the actor can resolve the ambiguity, and let the actor edit or discard the inferred rule.

Continuation

The agent holds a preference the actor never stated, and the actor cannot check it unless it is shown. What was taken from the demonstration is kept in words in memory, which is also where what the system picks up from ordinary use, without being shown, is kept and corrected. An example the actor points to is attached as reference material, and the demonstration lies in saying what about it to follow. A procedure recorded step by step becomes a workflow the actor can read and repair. Because a single demonstration fits many generalisations, a trial run over new cases lets the actor see which interpretation the system took before relying on it…

All connections
Precedes
Memory — tuning by demonstration leaves a learned preference, and memory is where the actor reads and corrects it
Workflow — A procedure recorded step by step becomes a workflow the actor can read and repair.
Trial run — Because a single demonstration fits many generalisations, a trial run over new cases lets the actor see which interpretation the system took before relying on it
Serves
Delegation — covers one way of conveying goals and preferences at delegation's set-up, and of repairing them later
Enacts
Malleability — the agent's behaviour is reshaped by an actor who cannot or need not describe the change
Complements
Reference material — An example the actor points to is attached as reference material, and the demonstration lies in saying what about it to follow.
Alternatives
Case correction — “Where the actor can show the right handling on the case more easily than state a rule for it, tuning by demonstration takes the place of editing the rule.”
Standing instructions — standing instructions hold what the actor can say, and tuning by demonstration takes in what they can only show
Rule composition — Standing instructions need the preference in words, and rule composition needs it in the system's terms.
Appears in
Delegating standing work: Putting it right, step 3

Resources & references