# How do I tag points in a standard?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Main menu", choose "Standards" and the standard, press "Add tag", type the tag, press "Save"; choose each step, type its tag, press "Save".

## Before you start

You need to be [signed in to GilbApp](http://support.gilb.com/help/how-do-i-sign-in-to-gilbapp) on a computer, with a standard in a vault you can write to, such as [your own vault](http://support.gilb.com/help/how-do-i-create-my-first-vault). The pictures show a made-up person on a test site; your screen shows your own name and address.

## Steps

1. 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".

   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.

   ![GilbApp with the "GO TO" panel open, with "Standards" under "YOUR SECTIONS" outlined in orange.](http://support.gilb.com/help/media/2f7771842dd46b46.png)
   What you see: 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.
2. Choose the standard in the list.

   Click the row of the standard, such as a process under the tab "Processes". It opens in the middle; a process shows the cards "Entry conditions", "Steps" and "Exit conditions", from top to bottom.

   Each row shows the standard's name and, under it, the last part of its address. If the list is long, type a word of the name in the box under "SEARCH PROCESSES". The other tabs, such as "Rules" or "Checklists", list other kinds of standard and open the same way. "+ New Process" makes a new process; [the answer on writing a new standard](http://support.gilb.com/help/how-do-i-write-a-new-standard) shows it. "← All processes", at the top of an open process, brings the list back.

   ![The Standards screen on the tab Processes, with the row of the process Open the bakery outlined in orange.](http://support.gilb.com/help/media/7b57e69e8d3215cb.png)
   What you see: In the middle, in the list under "SEARCH PROCESSES", the row Open the bakery is outlined, between two other made-up processes. Press the row to open that process.
3. Press "Add tag" under the standard's name.

   Under the standard's name, a line starts "The vault returned no ontology tag for this process."; press "Add tag" beside it. A box headed "ONTOLOGY TAG" opens, with "Clear", "Cancel" and "Save" under it.

   "ONTOLOGY TAG" is GilbApp's name for the tag: the standard's short name, unique in its vault, by which people and agents cite it. If the standard has a tag already, the line shows it and the button reads "Edit tag". On a rule document, a checklist or another kind the line names that kind instead of "process".

   ![The process Open the bakery open, with the button "Add tag" under its name outlined in orange.](http://support.gilb.com/help/media/730a3e158c997317.png)
   What you see: In the process card at the top, under the name Open the bakery, the line "The vault returned no ontology tag for this process." is followed by the outlined button "Add tag". Press it.
4. Type the tag in "ONTOLOGY TAG" and press "Save".

   Type the standard's tag, such as Bakery.Open, and press "Save". The box closes and the tag shows under the name.

   In the Kai-Zen method a tag is its parent's tag, a dot and one keyword in PascalCase, each word starting with a capital and run together, with no numbers. A new tag has no @ sign, no space and no invisible character, its letters are all of one script, such as the Latin alphabet, and it is at most 64 characters long in all. If GilbPlatform refuses the tag, the box stays open and shows why in red. "Cancel" closes the box and saves nothing. "Clear" removes a saved tag at once. GilbApp will not save a different tag over one already there; it says to clear the field first. Clear it, then press "Add tag" again. GilbApp lets you do this; in the Kai-Zen method a tag never changes once it is written, and if the text changes, the tag stays.

   ![The ONTOLOGY TAG box with Bakery.Open typed and the button "Save" under it outlined in orange.](http://support.gilb.com/help/media/f6d671826815860a.png)
   What you see: In the process card, under "ONTOLOGY TAG", the box holds the typed tag Bakery.Open. Under the box are "Clear", "Cancel" and the outlined button "Save". Press "Save" to give the process its tag.
5. Choose a step of the standard.

   Click the text of a step in the card "Steps". The right pane shows "Edit step", with its "TITLE", "TAG", "ENTITY URI" \(its address\), "TEXT" and "HANDS OFF TO".

   A point of a standard is one step, rule, question or other unit; on a rule document the pane says "Edit rule", and so on, and works the same. "Copy" under "ENTITY URI" copies the address. "HANDS OFF TO" links another standard, as [the answer on linking standards with hand-offs](http://support.gilb.com/help/how-do-i-link-standards-with-hand-offs) shows, and "🗑 Delete step" deletes the step, as [the answer on adding, editing, reordering or deleting a unit](http://support.gilb.com/help/how-do-i-add-edit-reorder-or-delete-a-unit-step-rule) shows. "✕" or "Cancel" closes the pane without saving.

   ![The process Open the bakery scrolled to its card "Steps", with the text of the step Light the ovens. outlined in orange.](http://support.gilb.com/help/media/41ca60903620bdc3.png)
   What you see: The page is scrolled down to the card "Steps", which reads "1 step, in order — all shown." The text of step 1, Light the ovens., is outlined. Press the text to open the step on the right.
6. Type its tag in "TAG" and press "Save".

   Type the step's tag in "TAG", the standard's tag, a dot and one keyword, such as Bakery.Open.LightOvens, and press "Save". The pane closes, and the step shows its tag before its text.

   If GilbPlatform refuses the tag, the pane stays open and shows why in red. A saved tag cannot be typed over: "Clear tag" empties it, and after "Save" you may type another. GilbApp lets you do this; in the Kai-Zen method a tag never changes once it is written, and if the text changes, the tag stays. Do the same for each step: choose it, type its tag and press "Save".

   ![The right pane Edit step with Bakery.Open.LightOvens typed in the box under "TAG", which is outlined in orange.](http://support.gilb.com/help/media/0a67d22ced6e9b8d.png)
   What you see: On the right, the pane "Edit step" is open. The box under "TAG" holds the typed tag Bakery.Open.LightOvens and is outlined. Under it are "ENTITY URI", "TEXT" and, at the foot, "Cancel" and "Save". Press "Save".

## Deeper

In the Kai-Zen method every point of a standard, each step, condition and rule, has a tag that is unique in its vault, made of the standard's tag, a dot and the point's keyword. A vault is one set of names: the tags of standards, of their points, of plan records and of stakeholders share it, so the method looks a tag up before writing it. Under a long standard name, keep the point short. A tag never changes once it is written; if the text changes, the tag stays.

GilbApp does not check a tag's form or whether it is taken; GilbPlatform refuses a tag another record in the same vault already has, and a new tag that breaks the limits in step 4. It does not check that an entry or exit condition's tag is unique; [the answer on writing entry and exit conditions](http://support.gilb.com/help/how-do-i-write-entry-and-exit-conditions) shows how to tag those.

GilbPlatform takes a tag only from someone who may write the standard. In the Kai-Zen method an agent changes a standard only with the go of a person who may write in the vault the standard is kept in.

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: Re-checked 2026-11-11: live GilbApp is now ebd9415e7a90de8c289eaa7bb02f40c8ee80cf79 \(https://gilb.com/app/version.json\) and GilbPlatform 498d29a0dec9a15d167f4b6b5d731382a6bcede0 \(https://id.gilb.com/version\). the diff from af0f04ee to ebd9415e touches no file this page cites \(src/components/process, RightRegion.tsx, gilbAppMenuRows.ts, the standards libs unchanged; processHooks.ts, records.ts and AppShell.tsx change only request headers and a palette note\); the diff from 4d008a55 to 498d29a0 changes sign-in, DPoP and grant slices, not the write gate or deletes. Line numbers above hold at ebd9415e. GilbApp code read \(unchanged at ebd9415e for these files\). Step 3: ProcessViewer.tsx:1981-1985 \(the tag under the name\); DocumentTag.tsx:168-208 \(empty line "The vault returned no ontology tag for this {documentNoun}. Nothing was invented — …", "Add tag" / "Edit tag"\), :107-165 \("Ontology tag" CSS capitals, "Clear", "Cancel", "Save", red error box\); RulesTab.tsx:719, :794 and the six other tabs \(onSaveDocumentTag; noun per kind\). Step 4: DocumentTag.tsx:93-105 \(closes only after the save resolves; Clear commits an empty tag at once, :125-133\); processDocTagEdit.ts buildProcessUnitTagPatch \(refuses a different tag over a served one: "… cannot be renamed in place … Clear the field to release the tag, then set the new one."\); StandardsSection.tsx:1034-1059 \(saveProcessUnitTag, re-read\); records.ts:270-315 \(refusal text passed through\). Step 5: ProcessViewer.tsx:1295-1308; StepEditPane.tsx:207-472; UnitIdentity.tsx:108-140. Step 6: StepEditPane.tsx:255-305 \(Tag, read-only once assigned, "Clear tag"\), :449-453 \(red error\), :157-173; RightRegion.tsx:280-282; ProcessViewer.tsx:1084-1088 \(tag pill before the text\); standardsFamilies.ts:222, 320, 413, 509, 607, 641, 668, 693 \(tagCarrierEditable true for every family\). GilbPlatform 4d008a55/498d29a0: src/write/tag-capture-observer.ts:114-116 \(write limits on a:unitTag\), src/write/tag-handle.ts:748-752 and errors.ts:265-284 \(409 collision in the vault; 400 tag-string-refused reasons at-sign, white-space, invisible-or-control, too-long, mixed-script, not-allowed\); routes.ts:822-827 \(write gate\). Standards \(200, 2026-11-10\): GilbPlatform.StandardRules.Tag \("Tag every point — step, condition, rule — with a tag unique in the vault: &lt;Standard\>.&lt;Point\>. Document tags and point tags share one namespace. … at most 64 characters for the whole tag; under a long standard name, keep the point short."\), .Owner; Kai-Zen.TagRules.Form, .Unique \("A vault is one namespace: specs, standards and stakeholders share it. … A GilbPlatform vault refuses a copy but does not check conditions"\), .Frozen. GilbVeda public read 2026-11-10: t:Tag, a:unitTag.
