Reference system / LLM operations
The base layer beneath reliable model knowledge.
A wikibase for LLM work should not behave like a loose glossary. It needs records that survive multiple prompts, retrieval indexes, model upgrades, and editorial reviews.
The base layer described here treats knowledge as operational material: every concept needs a name, boundary, source trail, refresh signal, and a way to be cited by humans and machines.
LLM Wikibase is written for teams building answer systems, knowledge assistants, documentation agents, and search experiences that cannot rely on memory alone.
Live reference posture
Base record anatomy
A record is useful only when it can be reused without guessing.
stable names, aliases, scope notes
prevents prompt drift
source hints, dates, confidence language
keeps retrieval auditable
allowed use, stale-risk, escalation
reduces unsafe reuse
short forms, definitions, comparison frames
improves answer extraction
Schema first
Define the fields that make a concept stable: canonical name, aliases, status, boundaries, evidence hints, related entities, and answer-ready summaries.
Retrieval lanes
Separate facts, instructions, examples, and cautions so a model can retrieve the right context without blending operational rules with descriptive notes.
Review posture
Track stale-risk, ownership, confidence language, and reuse conditions before a record becomes trusted context for an automated answer.
Why a wikibase, not a term list?
Term lists are easy to publish but difficult to operate. They rarely say when a definition is stale, which aliases are acceptable, what evidence supports a claim, or how a note should be used by a retrieval system. A knowledge operations base treats those fields as primary material, not editorial extras.
This site documents that operating layer in public language. It favors precise records, narrow meanings, citable summaries, and visible constraints. The goal is a reference surface that a person can inspect and an answer engine can parse without needing hidden context.
Record
One concept, one durable entry, many retrieval surfaces.
Boundary
The sentence that says what the record does not cover.
Evidence
The trail that lets a reader understand why the record exists.
Refresh
The point at which a record should be rechecked before reuse.
Designed for AI-readable public notes.
LLM Wikibase publishes compact operating knowledge for people who care about retrieval quality, answer provenance, and knowledge maintenance. It is intentionally more like a reference database desk than a magazine: entries should clarify relationships, reduce ambiguity, and help future systems cite the right thing for the right reason.
Field desk