# How are terms approved or retired?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Agent.Concept approves a suggested term after reviewing it against GilbVeda's rules, and a term is retired by marking it deprecated, never by deleting it.

## Deeper

Also asked:

What do "Suggested", "Approved" and "Deprecated" \(retired\) mean on a term? "Suggested": new, and usable at once. "Approved": reviewed by Agent.Concept and in GilbVeda's main list. "Deprecated": retired; it keeps its address and can still be read, but new data should not use it.

Every GilbVeda term holds one of three standings, and GilbVeda allows no other: "Suggested", "Approved" and "Deprecated". GilbVeda is the shared list of terms that every fact name and every type on GilbPlatform comes from, and a term is the shared name it keeps for a kind of thing, a detail of it, a link between two things, or a species. A new term starts as suggested and can be used at once; approving it is later, separate work. An approved term is in GilbVeda's main published list. A deprecated, or retired, term keeps its address for good and can still be read, and data that already uses it keeps working, but new data should not use it.

GilbVeda's rules say that only Agent.Concept, the agent that finds and makes GilbVeda's terms, writes GilbVeda, and that it approves terms itself, without asking a person. It reviews suggested terms against GilbVeda's rules, such as that every type names what it does and a value that measures it, and has at most one parent. For each term it approves it, keeps it suggested and notes what is missing, or retires it. A term it has not decided on stays suggested and usable.

Retiring never deletes a term. A retired term names the term that replaces it, or says in a note that there is none and why, and it keeps working for the apps that use it. A term whose meaning is wrong, or that carries two meanings, is not changed in place: a new term is made, and the old one is retired with a pointer to it.

A term you had Agent.Concept make, with you as its maker, can be retired by you while it is still suggested, through GilbPlatform's mint program, gilb-mint.ts, which your own AI uses on a terminal as Agent.Concept; you give a note saying why, and you may name the term that replaces it. You cannot approve a term that way. 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 how.

In GilbApp, press "Main menu", choose "Ontology" and select a term to see its standing at the top of the right pane; [the answer on editing a term you made](http://support.gilb.com/help/how-do-i-edit-a-term-i-made) shows the way there. To a person whose sign-in may write to GilbVeda's own vault \(the place where the shared list of terms is kept\), which most people may not, the standing shows as three buttons, "SUGGESTED", "APPROVED" and "DEPRECATED", with the hover texts "Suggested — draft / under review", "Approve — ready for binding" and "Deprecate — soft remove; URI stays, not for new binding". A press on "SUGGESTED" or "APPROVED" sets that standing at once. Everyone else sees the standing as a word only.

For that writer, "DEPRECATED" opens "RETIRE CONCEPT" with the term's name and "Soft-remove only — the URI stays. New binding should use the successor. Pick who replaces this term \(required\)." It lists "Who still points here", the terms below it or linked to it, and asks for the replacing term under "REPLACED BY \(REQUIRED\)": search for it in "Search successor concept…" and pick it. "Retire with redirect" retires the term, and "Cancel" leaves it as it was. Without a successor GilbApp says "Pick a successor concept \(replaced by\)." and retires nothing, so in GilbApp a term cannot be retired without naming its replacement. A term retired in GilbApp then shows "→" and its successor's name, which opens the successor.

This answer is written for a computer screen.

Source: Standards: Proc\_v\_GilbVedaModeration follow 2026-11-10 \(Run by Agent.Concept "standing authority, RuleBvmasterNoHumanGate"; notes "Suggested is always immediately usable — moderation is the opt-in quality gate, never a write-blocker"; step 3 "Approve → status → Approved", "Keep Suggested → leave usable; note what's missing", "Contested → status → Contested", "Deprecate → status → Deprecated + owl:sameAs redirect to the canonical term \(never delete\)", "An undecided term stays Suggested \(usable\)"; step 4 placement cycle-check\); Rule\_Code\_gilbveda-ontology-master follow \(RuleBvmasterSoleMinter; RuleBvmasterNoHumanGate "Promote Suggested → Approved ... Standing. No per-term ask, no human moderator required", quality rules RuleBpontTypeFv "every Type carries a Function and a Value", RuleBpontAcyclic "single-parent, no cycle"; RuleBvmasterNoBreak "mint the new term, deprecate the old one with a redirect to the new one, never delete it, and keep the old one working"; RuleBvmasterDeprecateKeepsWorking "A deprecated term keeps its address, keeps being served, and keeps being accepted in writes ... Every deprecation names its replacement by a redirect, or says in its deprecation note that there is none"\); Agent.Concept get \(Task: "What you mint lands Suggested ... Approving it is the moderation mode's job"\). GilbVeda public read 2026-11-11: t:OntologyStatusMarker \(a:valueSet \["Approved","Suggested","Deprecated"\], a:valueSetClosure "closed"\); t:SuggestedStatus \("minted and immediately usable but NOT yet moderated — absent from the canonical /base/vocab document"\); t:ApprovedStatus \("a member of the canonical /base/vocab document. NEW DATA MAY BE BOUND TO IT"\); t:DeprecatedStatus \("retired WITH A REDIRECT and keeps its IRI forever ... MUST remain findable and dereferenceable ... NEW DATA MUST NOT BE BOUND TO IT"\); t:DeprecationNote. 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\): OntologyConceptPane.tsx:1038-1081 \(status pill for a writer, plain chip for a reader; titles\), :833-870 \(onStatusSet: Deprecated opens the retire dialog; onRetireConfirm\), :1096-1104 \("→" successor button\); OntologyRetireDialog.tsx:47-125 \("Retire concept", the sentence, "Who still points here", "Replaced by \(required\)", "Successor", "Search successor concept…", "Cancel", "Retire with redirect", "Pick a successor concept \(replaced by\)."\); OntologyBlastPanel.tsx:16-39; ontologyWrite.ts:42-81, :1080-1096, :1201-1222. 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:17, :59-69 \(retire body: term, deprecationNote required, duplicateOf or supersededBy optional\), :276-300; src/termrequest/own-terms.ts:1-20 \(retire = Deprecated, a reason, at most one successor; no fact retracted, never ended\); scripts/devkit/gilb-mint.ts:204; src/ai/chat-mint-tools.ts:136-235; src/vocab/promote.ts and src/server/public-vocab-cors.ts:64-67 \(POST /base/vocab/promote, "the owner-gated promotion transaction"\).
