Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

G2P WikiLLM

A knowledge base for OpenG2P, structured for consumption by an LLM-based assistant — the G2P Advisor.

The wiki is built once at ingest time from authoritative sources (the OpenG2P GitBook documentation, GitHub repositories under github.com/OpenG2P, and the OpenG2P website) into a graph of cross-referenced markdown pages. The advisor reads these pages at runtime; it does not perform vector retrieval against raw text.

The repository lives at github.com/OpenG2P/g2p-wiki.

What is here

  • raw/ — immutable mirrors of the source material (GitBook docs, GitHub repos, website snapshot).

  • wiki/ — LLM-built, cross-referenced markdown pages: concepts, entities, source summaries, comparisons, flows, playbooks.

  • lessons/ — admin-curated, anonymised digests promoted from advisor sessions and expert elicitation.

  • elicitation/ — the knowledge-elicitation engine: the taxonomy (completeness spec), gap ledger, and interview guides.

  • tools/ — ingest, synthesis, elicit, and lint scripts.

Why this exists

Implementers, integrators, and government departments adopting OpenG2P need accurate, grounded answers from a single trusted surface. Vector-retrieval-only RAG systems often hallucinate because they search loose chunks of text without a stable structure. WikiLLM compiles the knowledge once into a curated graph, so the assistant reads from the same place every time and every claim can be traced back to its source.

The G2P Advisor (v2) is the primary consumer:

  • In chat mode, it reads wiki/index.md, drills into relevant pages, and synthesises an answer with [[wiki-link]] citations and links back to GitBook.

  • In project mode, it walks an implementer through phased implementation using the playbook pages in the wiki (e.g. the Registry use-case-implementation playbook) as the operating contract.

The advisor reads the wiki; it never queries GitBook or GitHub directly.

Sub-pages

  • Concept — WikiLLM — Karpathy's idea, the lens-not-mirror principle, and the elicitation concept.

  • Design — sources, folder structure, page types, conventions.

  • CLAUDE.md vs wiki/index.md — the two index-like files in the repo and how they differ.

  • Scripts — ingest, synthesise, elicit, lint, update — what each does, how to run it, and what to run when something changes.

  • Elicitation Engine — Operating Guide — the step-by-step loop for capturing tacit knowledge (scan → interview → synthesise → promote).

  • Roadmap & Automation — open TODOs and the plan for automatic updates when sources change.

Editing rules

  • Do not edit raw/ by hand. It is overwritten by ingest jobs.

  • Do not edit wiki/ by hand. It is regenerated by synthesis jobs.

  • Curated edits belong in lessons/ (via PR), or upstream in the source — for example, in the openg2p-documentation repo for GitBook content.

Last updated

Was this helpful?