# How do I edit a term I made?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Press "Main menu", choose "Ontology", search and select the term, click a field marked "· click to edit", type; only GilbVeda writers see it.

## 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 the right to write to GilbVeda; most people do not have it, and Deeper says what they can do. 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 "Ontology".

   Press "Main menu", next to your profile picture at the top left, and under "YOUR SECTIONS" choose "Ontology". The button shows the name of the section you are in, such as "Vaults".

   A panel headed "GO TO" opens; "Ontology" reads "The GilbVeda types and terms behind your data." It always opens on GilbVeda, the shared list of terms: the button at the top left of the screen reads "GilbVeda Ontology", the cursor is in the box marked "CONCEPTS", and below are three columns, "TYPES", "FUNCTIONS" and "VALUES". A type is a kind of thing; a Function is what a system does, written as an action; a Value is a perceived benefit, measured as a number. A term is the shared name GilbVeda keeps for a kind of thing, a detail of it, a link between two things, or a species. The right pane says "No concept selected". Resting the pointer on "Ontology" in the panel shows more choices under "IN ONTOLOGY"; you need none of them here.

   ![GilbApp with the "GO TO" panel open; "Ontology" under "YOUR SECTIONS" is outlined in orange.](http://support.gilb.com/help/media/5451cd11c5ac8e39.png)
   What you see: The panel headed "GO TO" is open over the window. In the left column under "YOUR SECTIONS", near the bottom, the outlined row reads "Ontology" and "The GilbVeda types and terms behind your data." Click it to open the Ontology screen.
2. Search and select the term in the box marked "CONCEPTS".

   Type at least three letters of the term's name in the box marked "CONCEPTS" and click the term in its column. The right pane shows the term.

   [The answer on finding a term](http://support.gilb.com/help/how-do-i-find-a-term) says more about the search, and about deprecated terms, which it hides at first. You can also click a term while browsing the columns, or the "Type" link in a record's "▸ DETAILS", which opens that type here.

   ![GilbApp's "Ontology" screen with a search in the box marked "CONCEPTS"; one match in the "TYPES" column is outlined in orange.](http://support.gilb.com/help/media/61ca16c88c206a4f.png)
   What you see: A name is typed in the box marked "CONCEPTS", and the matches fill "TYPES", "FUNCTIONS" and "VALUES". In "TYPES", one match is outlined. Click your term in its column; the pane on the right then shows it.
3. Click a field marked "· click to edit" and type the new text.

   Click the text under a field's name that has "· click to edit" after it, such as "DEFINITION \(ENGLISH MASTER\)", type the new text, and click outside the box to save it. Return also saves in a one-line box, and Escape leaves a field as it was.

   The name at the top is edited the same way. A type has "DEFINITION \(ENGLISH MASTER\)", a function "DOES \(ENGLISH MASTER\)" and "VERB", a value "DEFINITION \(DOES\)"; lower down are "LANGUAGES", where a term has names in other languages, "EXAMPLES", one per line, "EXTERNAL ALIGNMENT" and "PROVENANCE &amp; GOVERNANCE". "Saving…" shows while it saves. Saving changed text puts the term back to "SUGGESTED", not yet approved, even if it was approved. "+ NEW", "SUGGESTED", "APPROVED", "DEPRECATED", "Credit", "Licence", "Add picture" and "IS-A PARENT \(MOVE IN HIERARCHY\)" have their own answers; you do not need them here. If the fields show "Copy" instead of "· click to edit", your sign-in may not write to GilbVeda \(Deeper\).

   ![GilbApp's "Ontology" with your term open in the right pane; the box under "DEFINITION ENGLISH MASTER · click to edit", open with new text typed, is outlined in orange.](http://support.gilb.com/help/media/3ae3d335f00dd37c.png)
   What you see: Look at the right pane, below "PERMANENT URI". The outlined box under "DEFINITION \(ENGLISH MASTER\)" is open for typing, with the new definition typed in it. Type your text there, then click outside the box to save it; Escape leaves the field as it was. Other fields with "· click to edit" after their name work the same way.
4. On a value, edit "SCALE" and "METERS" the same way.

   Under "SCALE", click the text beside "① unit", "② rate", "Best" or "Worst", or the scale's description, and type; under "METERS", "+ Add meter" adds a meter and "Remove meter" takes one away. Each save puts the value back to "SUGGESTED".

   A value is a perceived benefit, measured as a number; its scale is what that number is counted in, from the worst level to the best, and a meter is the way the number is found. "VALUED BY — STAKEHOLDER AXIS \(SEPARATE\)" takes who the value matters to, one name per line, and "MEASURES \(FUNCTION\)" the function it measures, searched for and picked. A scale that is a term of its own shows under "SCALE \(FOUR-PART\)"; there "① unit", "② rate", "Best" and "Worst" change that scale term, not the value, and put the scale term back to "SUGGESTED"; "③ endpoints" cannot be edited. A term that is not a value has no such fields.

   ![GilbApp's "Ontology" with a value open at "SCALE ON THIS VALUE" and "METERS 1"; "+ Add meter" below the meter is outlined in orange.](http://support.gilb.com/help/media/0644b34a419d84df.png)
   What you see: Near the top of the right pane is the value's scale: its description, "① unit", "② rate", "Best" and "Worst". Click any of these texts to type a new one. Further down, under "METERS \(1\)", is the one meter with "Remove meter". The outlined "+ Add meter" below it adds another meter.

## Deeper

GilbApp shows these controls only to a person whose sign-in may write to GilbVeda's own vault, the place where the shared list of terms is kept, and most people may not. Everyone else sees each term read-only, with "Copy" beside its fields, and "Sign in as an ontology writer to create terms." when no term is chosen. A GilbVeda writer may edit any Type, Function or Value in GilbApp, not only one they made, and GilbApp edits the term where it is.

GilbVeda's own rules say that only Agent.Concept, the agent that finds and makes GilbVeda's terms, writes GilbVeda; your own AI acting as Agent.Concept counts as Agent.Concept. Under those rules a term in use may be added to at any time: a wider set of values, a new fact, a new link, an example. A change that could break an app using the term, such as a new meaning, a removed fact or a new parent, is made only when the meaning is wrong or one term carries two meanings, and then not in place: a new term is made, and the old one is retired with a pointer to the new one. Before it changes a term in use, Agent.Concept reads which apps use it.

A term you had Agent.Concept make starts as a suggested term with you as its maker. While it is still suggested, you can change it, or retire it, through GilbPlatform's mint program, gilb-mint.ts, which your own AI uses on a terminal as Agent.Concept. That program changes only terms you made, only while they are suggested, and never a term's address or its kind. In GilbApp's chat, Agent.Concept, the agent that finds and makes GilbVeda's terms, has tools to look terms up and to make new ones, but none to change, approve or retire a term. [The answer on changing or retiring a term you minted](http://support.gilb.com/help/how-do-i-change-or-retire-a-term-i-minted) shows the commands and what each answer means.

Every change is kept: the term's "CHANGE HISTORY" in the right pane shows who changed it, when and what. [The answer on having a concept found or made in GilbVeda](http://support.gilb.com/help/how-do-i-have-a-concept-found-or-made-in-gilbveda) shows how to ask Agent.Concept for a new term.

This answer is written for a computer screen.

Source: GilbApp ebd9415e7a90de8c289eaa7bb02f40c8ee80cf79 \(https://gilb.com/app/version.json read 2026-11-11, dirty false\); every GilbApp file cited is byte-identical to af0f04ee \(between af0f04ee and ebd9415e, the cited files: empty\), so line numbers are read from the unpack \(no checkout\): src/shell/gilbAppMenuRows.ts:236-254 \("Ontology", "The GilbVeda types and terms behind your data."\); src/components/ontology/OntologySection.tsx:48 \("GilbVeda Ontology"\), :783-823 \("Concepts" uppercase, "Search concepts…"\), :918-980 \(columns "Types", "Functions", "Values"; OntologyFacetColumn.tsx:99-112 uppercase\); OntologyConceptPane.tsx:153-179 \(canWrite = sessionCanWriteOntology, readers get nav + copy only\), :617-650 \(saveField; content edit lands Suggested\), :951 \("Sign in as an ontology writer to create terms."\), :969-985 \("+ New", uppercase, title "Create a new Type, Function, or Value"\), :1845-1870 \("Languages", uppercase, "Select language"\), :1020-1036 \(usage chip "N Apps", uppercase, "▸"\), :1038-1081 \(status chip or pill\), :1093 \("Saving…"\), :1103-1118 \(Label inline edit\), :1241 \("Permanent URI"\), :1265-1282 \("Definition \(English master\)", "Does \(English master\)", "Definition \(Does\)"\), :1408-1415 \("Verb"\), :1597-1625 \("Examples"\), :1545-1590 \("External alignment"\), :1630-1720 \("Provenance &amp; governance"\), OntologyHistoryPanel.tsx:73-74 \("Change history", uppercase\); inlineEdit.tsx:12-60 \(dt uppercase, "· click to edit", "Copy" for a reader\), :120-176 \(blur or Enter commits, Escape cancels\), :230-275 \(multi-line: blur commits\); src/lib/base/ontologyWrite.ts:1-11 \("Content edits ... land Suggested"; PUT on the veda vault\), :64-81 \(sessionCanWriteOntology: write on a vault whose id holds veda.gilb.com; "most people only have personal-vault write and must see a read-only concept pane"\), :1092-1096 \(content edit sets Suggested\); ValueFacets.tsx:298-400 \("Scale", "scale", "① unit", "② rate", "Best", "Worst", "Scale description"\), :170-200 \("Valued by — stakeholder axis \(separate\)", "who this value matters to · one term name per line"\), :266-296 \("Measures \(Function\)"\), :660-770 \("Meters \(n\)", "Remove meter", "+ Add meter"\), :819-823 \(section titles uppercase\). GilbPlatform 498d29a0dec9a15d167f4b6b5d731382a6bcede0 \(https://id.gilb.com/version read 2026-11-11, dirty false\); every platform file cited is byte-identical to 4d008a55 except docs/BASE-DEVELOPER-GUIDE.md, whose changes touch none of the parts cited; code read at 498d29a0: src/routes/term-mint.ts:1-26 \(any signed-in person mints through Agent.Concept; change and retire own terms\), :106-116 \(NotYourTerm, TermNotSuggested, TermFieldImmutable\), :240-274; src/termrequest/own-terms.ts:1-39 \(own = a:termMintedBy is the caller and status Suggested; CHANGEABLE list: identity, key and kind carried forward\); scripts/devkit/gilb-mint.ts:186-205 \("change one of YOUR Suggested terms", "retire one of YOUR Suggested terms"\); src/ai/chat-mint-tools.ts:136-235 \(chat tools read\_term, lookup\_term, lookup\_taxon, mint\_term, mint\_taxa, ask\_agent\_concept: none changes, approves or retires\). Standards: Agent.Concept get 2026-11-10 \(Task: "What you mint lands Suggested, with the person as its minter"; "On a terminal, the person's own AI acts as you, with the mint client gilb-mint.ts"\); Rule\_Code\_gilbveda-ontology-master follow 2026-11-10 \(RuleBvmasterSoleMinter "Only Agent.Concept writes ontology ... A person's own AI acting as Agent.Concept with the mint kit is Agent.Concept for this rule"; RuleBvmasterUsageFirst; RuleBvmasterNoBreak "You may add to a live term at any time ... A change that could break an app using the term \(a narrower encoding, a new meaning, a removed fact, a moved parent\) is made only when it is necessary, and never in place ... mint the new term, deprecate the old one with a redirect"\). GilbVeda public read 2026-11-11: t:SuggestedStatus, t:ApprovedStatus, t:OntologyStatusMarker \(a:valueSet Approved, Suggested, Deprecated; closed\). ValueFacets.tsx:444-560 \("Scale \(four-part\)"\) at ebd9415e: the four-part box, its ① unit, ② rate, Best, Worst boxes and the read-only ③ endpoints line.
