MyJackfruit

Help
Browse topics · For developers

For developers

← For developers

How do I change or retire a term I minted?

Short answer

Read the term to check it is yours and Suggested, then send the whole changed member with gilb-mint.ts change, or retire it with gilb-mint.ts retire.

Before you start

gilb-mint.ts signed in as the person who minted the term, as the answer on minting a term shows.

Words used here (1)
record
A record is one piece of data with its own address, such as a person, a place, a thing or a note.
Steps
  1. Read the term and check it is still yours.

    Read the term with no token, and check that a:termMintedBy is your address and a:ontologyStatus is Suggested:
    GET https://veda.gilb.com/base/t/<Name>

    More about this

    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. whoami in the mint program shows your address. Only a term you minted, and only while it is Suggested, is yours to change or retire. Once it is Approved or Deprecated it is not, and a term with no a:termMintedBy, such as one made before this way of minting, is no one's to change here.

  2. Change it by sending the whole member.

    Write the member again (the term's one record, as in the minting file) with every key, its term naming the term, and send it:
    node ~/.gilb/kit/gilb-mint.ts change <member file>

    More about this

    What you send replaces label, does, example, subTypeOf, providesFunction, encoding, cardinality, measures, valueSubject, valuedBy, scale, hasMeter, confidence, justifiedBy and hasValue; every other fact is kept. The name, nodeKind and predicateAttribute cannot change: retire the term and mint a new one. To change several at once, such as a term and the Value that measures it moving to another Function together, send { terms: [ ... ] }: they land together or not at all. A 200 answer names the term under changed, still Suggested. app on a change answers 400, as a change records no use.

  3. Or retire it, saying why.

    Write the term, the reason and at most one successor, and send it:
    node ~/.gilb/kit/gilb-mint.ts retire <retire file>

    More about this

    The file is { term: t:<Name>, deprecationNote: <why>, supersededBy: t:<Other> }; use duplicateOf in place of supersededBy when the term is a duplicate of the other, or leave both out. The successor must be a live term, Suggested or Approved, and not the term itself; otherwise the answer is 422 MintPackageGaps and nothing is retired. A 200 answer names the term under retired, with the status Deprecated. Retiring never deletes: the address keeps answering, with a:deprecationNote and its successor, apps that use it keep working, and a search for its name answers REFUSED with the successor.

Deeper

403 NotYourTerm: someone else minted it, or no one did. 409 TermNotSuggested: it has been reviewed and is no longer yours to change. 404 TermNotFound: no term has that name. 409 TermFieldImmutable: the change tries to alter nodeKind or predicateAttribute. 409 TermHasMultiRowFact: a fact written another way holds more than one row, and nothing was written. 400 MintPackageInvalid names a wrong shape or a blank deprecationNote, and 422 MintPackageGaps what the change would leave taken, missing or of the wrong kind, or a successor that is not a live term or is the term itself. 409 MintFloorMoved: send it again. The same gate as minting comes first: 401 with no sign-in, 403 NotThroughAgentConcept without the pass. A change or a retirement does not count against the daily mint limit.

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.

From your own code, the routes are POST https://veda.gilb.com/base/vocab/mint/change and POST https://veda.gilb.com/base/vocab/mint/retire, with the person's token, a new DPoP proof (a short signed note your app makes for one request) and the pass, as the answer on minting a term shows; example 1 shows them. In GilbApp's chat, Agent.Concept has tools to look terms up and to make new ones, but none to change, approve or retire a term. In GilbApp, a person who may write to GilbVeda's own vault edits terms in Ontology; the answers on editing a term you made and on how terms are approved or retired show how. A species you sent is changed or retired in the same way; the answer on minting and looking up species shows how.

The Developer Guide, GilbPlatform's guide for people who build apps on it says in its chapter Dev.Guide.Vocabulary, https://appbuilder.gilb.com/base/e/06gkzpwtj1wm58yf6zng0xdtbm, that vocabulary changes only add; changing or retiring your own term is not in it yet. It can be read with no sign-in, as data for programs and AIs rather than as a web page.

Source: GilbPlatform 498d29a0 (live at https://id.gilb.com/version, read 2026-11-11): src/routes/term-mint.ts:1-27, :50-69 (change body = one whole member or { terms }; retire body term, deprecationNote 1-4000, duplicateOf, supersededBy, additionalProperties false), :106-116 (403 NotYourTerm, 409 TermNotSuggested, 409 TermFieldImmutable, 409 TermHasMultiRowFact, 404 TermNotFound, 422 MintPackageGaps), :240-274 (change: 400 for app, changed one object or a list, status Suggested), :276-301 (retire: identity t:<Name>, blank note 400, at most one successor 400, 200 retired status Deprecated); src/termrequest/own-terms.ts:1-43 (OWN = live a:termMintedBy is the caller and status Suggested; a term with no minter refused; CHANGEABLE list; retire = Deprecated, a:deprecationNote, owl:sameAs or a:supersededBy, nothing retracted, never ended), :99-124 (messages; nodeKind and predicateAttribute cannot change), :236-286 (successor live Suggested or Approved, not itself; gaps); src/termrequest/mint-quota.ts:1-6 (a change or retire never reaches the quota); src/termrequest/mint.ts:245-250 (newIdentityName: the name is the identity); src/ai/chat-mint-tools.ts:135-230 (no change or retire tool). src/routes/_mint-gate.ts:1-42 (one gate for terms and GilbLife: host 404, mayMintTerms 401/403, vault served and local 503, pass 403 NotThroughAgentConcept New ontology is minted through Agent.Concept only. ...), :92-128; src/auth/mint-pass.ts:1-66 (pass issued by the server for an Agent.Concept turn; header x-base-mint-pass; aud base:mint:vocab or base:mint:life; 15 minutes; sub = the person); src/routes/ai-claude-code.ts:271-298 (POST /base/ai/claude-code/context: mintPasses only on an Agent.Concept turn and when mayMintTerms passes), :114-127 (body: userText required, agent, agentEntry, contentVaultIds, turnId); src/auth/open-mint-standing.ts:1-110 (a signed-in person or a bound AI; computer credential or unbound machine 403 NotAPersonToMint; no http principal 401 SignInToMint). scripts/devkit/gilb-mint.ts:41-45 (id.gilb.com, veda.gilb.com, life.gilb.com), :186-239 (usage text), :271-317 (signin: request-code; code: verify-code with the kit's own P-256 key; ~/.gilb/mint-credential.json 0600; expiry check), :324-357 (passFor: POST <base>/base/ai/claude-code/context with agent Agent.Concept, mintPasses.vocab|life; needsPass for POST /base/vocab/, /base/life/mint, /base/term-requests), :502-540 (search: one https IRI = GilbLife taxonID; words = term-requests then GilbLife scientificName; --app prints usage: recorded for / usage: NOT recorded for), :542-581 (mint/change/retire routing; the shipped example refused locally, exit 2); scripts/devkit/README.md:21-36 (Node 22.18+ or 23.6+; 6-digit code 10 minutes; credential 7 days), :38-83 (the loop, answers, exit codes 0/1/2, dropped connection), :85-143 (GilbLife), :171-184 (a member); scripts/devkit/example-package.json (an attribute and its Value). Public reads, no token, 2026-11-11: https://veda.gilb.com/base/t/<a Suggested term> 200 with a:ontologyStatus Suggested and no a:termMintedBy; a read of a term retired through this route 200 with a:ontologyStatus Deprecated, a:termMintedBy, a:deprecationNote and a:supersededBy (the minter's address not used on the page). Dev.Guide.Vocabulary.Additive (A 06gkzpwtj1wm58yf6zng0xdtbm). Shared sentences, word for word: term; GilbVeda's rules and the add-only paragraph; the chat has no change tools; REFUSED with successors.

For developers

curl

change-and-retire.sh

# Is the term still yours? Check a:termMintedBy and a:ontologyStatus. No token is needed.
curl -s "https://veda.gilb.com/base/t/<Name>"

# Change it: the whole member, every key, its term naming it. The pass as in minting.
curl -s https://veda.gilb.com/base/vocab/mint/change \
  -H "Authorization: DPoP <sign-in token>" \
  -H "DPoP: <a new proof for POST https://veda.gilb.com/base/vocab/mint/change>" \
  -H "X-Base-Mint-Pass: <mintPasses.vocab>" \
  -H "Content-Type: application/json" \
  --data @member.json
# 200: {"changed":{"term":"https://veda.gilb.com/base/t/<Name>","entity":"<address>","status":"Suggested"}}

# Or retire it, with the reason and at most one successor.
curl -s https://veda.gilb.com/base/vocab/mint/retire \
  -H "Authorization: DPoP <sign-in token>" \
  -H "DPoP: <a new proof for POST https://veda.gilb.com/base/vocab/mint/retire>" \
  -H "X-Base-Mint-Pass: <mintPasses.vocab>" \
  -H "Content-Type: application/json" \
  --data '{"term":"t:<Name>","deprecationNote":"<why>","supersededBy":"t:<Other>"}'
# 200: {"retired":{"term":"https://veda.gilb.com/base/t/<Name>","entity":"<address>","status":"Deprecated"}}

Checked against GilbApp d529620.