How do I tag and link specs?
Short answer
Press + New in Plan, choose the kind, type a tag, press Create, press + Add Information, choose Type, search and select the GilbVeda type.
Before you start
You need to be signed in to GilbApp on a computer, with a vault you can write to, such as your own vault. 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.
- 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.
- record
- A record is one piece of data with its own address, such as a person, a place, a thing or a note.
- virtual folder
- A virtual folder is a view that groups records and files without moving them; each may sit in several folders.
- short name
- A short name is the one word you give one AI on one computer, such as gilb-example; it keeps that AI's key and tools apart.
- agent
- An agent is your AI following one written procedure, its standing instructions, for one kind of work.
Steps
Press Main menu at the top left and choose Plan.
Press Main menu, next to your profile picture at the top left, and under YOUR SECTIONS choose Plan. The button shows the name of the section you are in, such as Vaults.


Show as text
In the GO TO panel that opens from "Main menu" at the top left, look under YOUR SECTIONS on the left. The outlined row is "Plan", with the line "Your Kai-Zen plan: Functions, Values, Development Resources and Solutions." Press it to open the Plan screen.
More about this
A panel headed GO TO opens; Plan reads Your Kai-Zen plan: Functions, Values, Development Resources and Solutions. You can also press the Plan button on the card of a vault (the place where a person or a group keeps their records) in Vaults. The Plan screen lists your plan records and has the views Grid, Graph, Both and Card.
Press + New.
Press + New at the top right of the Plan screen. With no record selected, the type dialog opens at once.


Show as text
Look at the top right of the Plan screen, just left of the Details pane. The outlined button is "+ New". Press it; with no record selected a dialog headed "New function" opens with its "TYPE" list.
More about this
If a record is selected, New first offers five choices: Create a record and link it to the selected record, Link the selected record to a record that already exists, Create a record on its own, Create a virtual folder and Upload a file. Choose Create a record on its own. A new spec needs nothing else; the others make a record joined to the selected one, link two records that already exist, make a virtual folder or upload a file. In Plan, the GO TO panel also has New plan record, which does the same.
Under TYPE, choose the kind of spec.
In the list under TYPE, choose what the spec is, such as Function, Value or Solution. A spec is a requirement written in your plan; this list says which kind of plan card it is.


Show as text
In the dialog headed "New function", the list under "TYPE" is scrolled to show "Solution", between "Value" and "Solution Constraint". It is outlined. Choose the kind of spec you are writing; here it is "Solution".
More about this
The dialog opens headed New function with Function chosen; after you choose, its heading names the kind, such as New solution. The chosen type then shows under TYPE with a DEFINITION read from GilbVeda, the shared list of terms; you need not read it. × beside the type brings the list back. A search box above the list narrows it as you type, and Close at the top of the dialog closes it like Cancel; you need neither. ↗ at the end of a row shows what GilbVeda says about that type; you do not need it. Cancel closes the dialog without making anything. Where it shows Back instead, Back returns you to the five choices.
Type a tag in TAG and press Create.
Type a tag in TAG, check CREATE IN, and press Create. A tag is the short name of a plan record: an area, a dot and a keyword, such as Save.LocalFirst.


Show as text
The dialog is headed "New solution", with the type's "DEFINITION" under "TYPE". "TAG" holds the tag you typed. At the bottom right, the outlined button is "Create". Press it.
More about this
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. For a spec the first part is its area, such as Save in Save.LocalFirst; the level and the kind go on their own lines, not in the tag. The box shows a pattern such as Area.Keyword, e.g. Usability.Learn until you type. If the tag has a space or another character a tag may not hold, GilbApp says why under the box and makes nothing; where joining the words fixes it, a button starting with Use offers the joined tag. With the tag empty the screen says Give it a Tag first: a Plan card is named by its Tag. If the tag is already used in that vault, it says is already used in this vault. Pick another.
If it has parts, under Description, press + Part, type a Keyword and Text, and press Add.
Under Description, press + Part, type a one-word Keyword and the Text, and press Add. Each part gets its own tag: the card's tag, a dot and the Keyword, such as Save.LocalFirst.Sync.


Show as text
On the new card, under "Description", the add row is open: the short box holds the keyword and the long box the text. Below them, after "Discard", the outlined button is "Add". Press it.
More about this
The Kai-Zen method splits a Solution's description into such parts, each with a full tag of its own. The Keyword is letters only, starting with a capital; otherwise the screen says Keyword: letters only, starting with a capital, e.g. Sync. On a Value the parts sit under Ambition Level. To put a part under another, press Done, click the part's text and press + Sub-part: its tag is its parent's tag, a dot and its Keyword, such as Save.LocalFirst.Sync.Queue. In Paste parts, a line starting with a dash and a space becomes a sub-part of the line above. In edit mode → also moves a part under the one above, but a moved part keeps its old tag. The answer on writing a Solution in your plan shows the other part buttons.
Press + Add Information and choose Type.
At the foot of the card, press + Add Information, and in the list under Plan choose Type. The card shows a Type line, and a box that shows Search GilbVeda types… opens with the cursor in it.


Show as text
After "+ Add Information" at the foot of the card, a list opens with "Search" and "Cancel" at the top and the heading "Add information". Under "Plan", the outlined choice is "Type". Click it.
More about this
This Type is the kind of thing the spec is about, chosen from the types in GilbVeda: for a spec about tennis, the type Tennis. It is not the Type: on the line under the card's header, which says whether the card is a Function, a Solution and so on. The + beside Done opens the same list; its Search box narrows the list, and Cancel closes it. If Type is not in the list, the card already shows the line: press Choose a type or Change on it.
Search and select the GilbVeda type in Search GilbVeda types….
Type a word for the kind of thing in the box that shows Search GilbVeda types… and select the type in the list. The card's Type line then shows it.


Show as text
The card now has a "Type" part. Under "TYPE", the outlined box holds the word you typed, with "×" at its right; the matching GilbVeda types are listed under it. Select the one that fits.
More about this
The list holds types, functions and values from GilbVeda. With none found it says No type, function or value matches and what you typed; if GilbVeda could not be asked, it says GilbVeda could not be searched just now, so nothing can be shown. GilbApp makes no new term here. It lists only terms GilbVeda already has; for one it lacks, ask Agent.Concept, the agent that finds and makes GilbVeda's terms (Deeper). No GilbVeda type records that none fits, and Cancel closes the box. Once a type is chosen, ↗ beside it shows what GilbVeda says about it, and Change picks another and replaces it at once; only an earlier concept the card still holds from before brings the question Replace the earlier concept …?.
Press Done when you have finished.
Press Done at the top right of the card. What you typed is already saved.


Show as text
The card is scrolled to the top and is still in edit mode. At the top right, beside the box with the tag, the outlined word is "Done". Press it when you have finished; each field was saved when you left it.
More about this
The card's header shows its tag. In edit mode the header is a box holding the tag, and GilbApp lets you change it there; in the Kai-Zen method a tag never changes once it is written, and if the text changes, the tag stays.
Deeper
In the Kai-Zen method every spec has a tag, and the tag is unique in its vault: specs, standards and stakeholders share one set of tags, so the method looks a tag up before writing it. GilbApp refuses a tag already used in the same vault. 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. GilbApp refuses only what those limits forbid; a tag with no dot, with a number or in lower case is accepted, though the method asks for the form in step 4.
When Kai-Zen writes a Function or a Value (a perceived benefit, measured as a number), it first asks Agent.Concept, the agent that finds and makes GilbVeda's terms, what GilbVeda holds for that kind of thing, such as Functions and Values used before, and reuses or adapts what fits. An agent is your AI following one written procedure, its standing instructions, for one kind of work. When the Function or Value is written, Kai-Zen hands it to Agent.Concept, which adds the general Function or Value to GilbVeda, or links it to the one already there; the link goes on the card's GilbVeda type line. No other agent finds or makes a GilbVeda term. If it cannot answer yet, the line says that Agent.Concept decides, and the work goes on.
You can ask Agent.Concept yourself for a term GilbVeda does not have: in GilbApp's chat, choose Agent.Concept - Master of Concepts in the agent list and say what the spec is about; the answer on chatting with an agent in GilbApp shows the chat. Agent.Concept looks the term up first, by its name and by its meaning. If it finds one, it gives you that one; if not, it makes it at once, as a suggested term with you as its maker, without asking anyone to confirm. If you have not named the app the term is for, it asks only that.
Links between specs, such as the Functions a Solution serves or the Values it changes, are written on the cards themselves; the answers on writing a Solution in your plan and on reusing a Solution or a Constraint show them.
This answer is written for a computer screen.
Source: GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (https://gilb.com/app/version.json read 2026-11-09, dirty false); code from the unpack (at af0f04ee). Steps 1-2:. recordTypes.ts:386-482 (kinds with a Tag box). Step 4: recordTypes.ts:386-482 (placeholders Area.Keyword, e.g. …); ConnectedCreateDialog.tsx:319 (Give it a Tag first: …), :495-520 (tagDraftProblem note under the box and Use <tag> button; nothing sent while a problem stands, :1011), :1207-1214 and planLinks.ts:213 (The tag … is already used in this vault. Pick another.); tagDraft.ts:35-61 (refusal reasons: at-sign, white-space, invisible-or-control, too-long, mixed-script, not-allowed). Step 5: planParts.ts:16 (KEYWORD_MESSAGE), :25 (KEYWORD letters only, capital first); DescriptionHelp.tsx:132-166 (part tag = card tag, a dot, the Keyword; '+ Sub-part' after clicking the part's text; 'A sub-part you add gets its parent's tag, a dot, and its Keyword. A part you move keeps its tag.'), :202-262 (Paste parts: '- Keyword: text' = a sub-part of the line above); PlanDescriptionParts.tsx:1777-1787 ('+ Sub-part' only when the part is open and the card is not in edit mode); planKinds.ts:102 (description shown as Ambition Level on a Value). Step 6: AddInformation.tsx:21-140 (+ Add Information, sheet Add information, Search, Cancel, groups under section headings); CardGroup.tsx:20-33 (plan groups under Plan), :175 (an empty group is hidden unless opened); PlanFunctionForm.tsx:2066-2067 (group Type, keepInEdit false); PlanTypeField.tsx:120-180 (Choose a type pressed by the pick, Change, No GilbVeda type, Cancel, Search GilbVeda types…). Step 7: TypeChooser.tsx:30-35 (mints nothing), :418-441 (No type, function or value matches “…”., GilbVeda could not be searched just now, so nothing can be shown.); PlanFunctionForm.tsx:2074-2110 (replace ask when another type is set). Step 8: RecordDetail.tsx:3003-3035 (PlanHeaderTitle: in edit mode an input labelled Tag), :1258-1263 (taken-tag notice on a changed tag). Standards (2026-11-09, all 200): Kai-Zen.TagRules (Form, Top, Condition, Spec, Unique, Frozen), Kai-Zen.SolutionRules (Description, SubTags, Assumption, Tag), Kai-Zen.SolutionTemplate, Kai-Zen.ConceptRules (Link, Mint, Open, Reuse, Share, Grow), Agent.Concept (Role, Task: lookup by name and meaning, mint at once, Suggested with the person as minter, no one confirms). GilbVeda public read: t:Tag, a:unitTag, a:ontologyTerm, t:SpecificationElement, t:Assumption (all 200).
Checked against GilbApp d529620.