← Back to How do I run a standard in order from code?
How do I follow a hand-off to another standard?
Short answer
Press Main menu, choose Standards and the standard, press the tag after ↳ hands off to, ← All processes, and choose your first standard.
Before you start
You need to be signed in to GilbApp on a computer, with a standard in a vault you can read, such as your own vault, whose step hands off to another standard. The pictures show a made-up person on a test site; your screen shows your own name and address.
Words used here (6)
- GilbApp
- GilbApp is the app, opened in a web browser at https://gilb.com/app, where you open, fill and share your vaults.
- record
- A record is one piece of data with its own address, such as a person, a place, a thing or a note.
- entry condition
- An entry condition is something that must be true before a process may start; a process starts only when its entry conditions hold.
- exit condition
- An exit condition is what must be true before a process may finish; when it is true, the process hands back.
- agent
- An agent is your AI following one written procedure, its standing instructions, for one kind of work.
- Kai-Zen
- Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Steps
Press Main menu at the top left and choose Standards.
Press Main menu, next to your profile picture at the top left, and under YOUR SECTIONS choose Standards. The button shows the name of the section you are in, such as Vaults.


Show as text
The panel headed "GO TO" covers the screen. In the left column under "YOUR SECTIONS", the row "Standards" with the line "Processes, rules, templates and checklists." is outlined. Press it to open the Standards screen.
More about this
A panel headed GO TO opens; Standards reads Processes, rules, templates and checklists. Standards opens on the vault you picked in Vaults, or on your own vault if you picked none; a vault is the place where a person or a group keeps their records. It opens on the tab Processes, with Process chosen in the row under the tabs. A process is a standard that holds work: entry conditions, steps in order, and exit conditions; a standard is a written procedure, rule set, form or other guide that people and agents follow as they work. On the right, VAULT changes the vault, STANDARDS GROUP shows only the standards of one group, and + New group, shown only where you may write in the vault, makes a group; you need none of them here.
Choose the standard in the list.
Click the row of the standard whose step hands off, such as Open the bakery. It opens in the middle of the screen.


Show as text
In the middle, in the list of processes, the row Open the bakery is outlined. Press it to open the standard that holds the hand-off.
More about this
The answer on reading a standard says what the open standard shows. If the standard is under another tab, such as Rules, press that tab first; the answer on finding a standard shows how to look for it.
Press the tag after ↳ hands off to.
Under the step, after ↳ hands off to, press the other standard's tag, such as Bakery.CheckOvens, followed by →. That standard opens in its own tab; a link to one rule or step of a standard opens the standard that holds it.


Show as text
In the card "Steps", under step 1 Light the ovens., the line "hands off to" ends in the outlined tag Bakery.CheckOvens with an arrow. Press the tag to open the standard it names.
More about this
A hand-off is a link from a point of a standard, such as a step, to the standard that does the part of the work the point names. If the link points into another vault you have been given access to, that standard opens there and VAULT changes to that vault. A grey tag with a short note does not open: CHECKING while GilbApp looks; NOT IN THIS VAULT or NOT FOUND when it is missing; NOT A STANDARD when it points at another kind of record; NOT CHECKED when it is in a vault you have not been given access to, or could not be read; ADDRESS ONLY for a link, held in another vault, into the vault that keeps Kai-Zen's standards. Resting the pointer on a tag says more.
Press ← All processes when you are done.
When you have read it, press ← All processes at the top of the standard. The list of its tab comes back.


Show as text
The process Check the ovens is now open in the middle, with its tag Bakery.CheckOvens. At the top left, above its card, the outlined button "All processes" with a left arrow takes you back to the list. Press it when you are done.
More about this
On another kind of standard the button names that kind, such as ← All rule documents or ← All ProcessCard records. GilbApp has no button that goes back to the standard you came from, and it changes the page's address in place when it opens a hand-off, so your browser's back button does not return to it either. If the other standard was in another vault, choose your vault again under VAULT on the right.
Choose the standard you came from.
Click the row of the standard you came from, and go on from the step after the one that handed off. If it is a process under Processes and you are on process cards, press Process under the tabs first.


Show as text
The list of processes is back in the middle. The row Open the bakery, the standard you came from, is outlined between Check the ovens and Water the plants. Press it to go back to that standard.
More about this
In the Kai-Zen method a hand-off from a process step to a process is a call and a return: you do the other process, and when it has finished, the step that handed off goes on with its next step. From any other point, such as a rule, a hand-off is a link to read: you go to the other standard for what the point names there.
Deeper
Also asked:
What is a hand-off between standards? A link from a point of a standard, such as a step, to another standard, or a point in one, that does the job the point names. From a step, the other standard is followed, then the first goes on with its next step.
GilbApp shows hand-offs on the points of a standard, such as its steps, rules and questions, and on its entry and exit conditions. Hand-offs are added in a point's pane on the right; the answer on linking standards with hand-offs shows how.
If a step holds a link GilbApp cannot read, the step shows how many, such as 1 stored hands-off value this app cannot read.
In GilbApp today a link to a standard in a vault you have not been given access to does not open, even if anyone may read that vault, such as the vaults that keep GilbPlatform's own standards; the answer on the standards packs tells more.
This answer is written for a computer screen. In a window narrower than 840 pixels, such as a phone, the side panes are hidden and the right pane is Detail in the bar at the bottom.
Source: GilbApp af0f04ee (https://gilb.com/app/version.json read 2026-11-10), code read: step 1; step 2 StandardsSection.tsx:427-448; step 3 components/process/ProcessViewer.tsx:745-790 (↳ hands off to, one chip per link, unreadable count), :937-949 (chip button: label + →, hover title), :839-905 (resolved chip states and notes checking, not checked, not a standard, not in this vault), :914-934 (address only; other-vault notes checking, not found, not a standard, not checked with title … is not in one of your vaults, or could not be read, so it was not opened), components/process/handoffTargets.tsx:51-62 (each kind opens in its own tab), :151-196 (a unit opens the document that holds it), :203-235 (other vault: opens there), lib/base/handsOffReach.ts:80-87, :142-164 (another vault only if in the session's reach; otherwise outside), lib/base/handsOffNoLinkList.ts:1-2 (kaizen.gilb.com/base shown as address only), components/AppShell.tsx:187-203 (paramsForOpenStandard: switches the vault when the target is in another vault), :1094-1098 (openStandard with replace: true); step 4 StandardsBackControl.tsx:33-52, StandardsSection.tsx:838-841 (All processes / All {kind} records), RulesTab.tsx:658 (All rule documents), lib/base/standardKinds.ts:108-120 (ProcessCard); step 5 StandardKinds.tsx:35-43; Deeper ProcessViewer.tsx:1315-1336 (step hand-offs) and :518-526 (condition hand-offs), lib/base/processTypes.ts:75-77 (N stored hands-off value(s) this app cannot read). GilbPlatform 4d008a55: src/authz/reachable-vaults.ts:242-243. Standards (2026-11-10, 200): GilbPlatform.StandardRules.HandOff ("Call and return. A step's Hands off to points at a child; when the child exits, the caller goes on with its next step."), .Link. GilbVeda a:handsOffTo (public read 2026-11-10: from a process step to a Process it is CALL AND RETURN; "Everywhere else it is a FOLLOWED LINK: the reader goes to Y for what X names there").
Checked against GilbApp d529620.