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

G2P Advisor

A hosted, login-based web app that walks an implementer through deploying OpenG2P. It collects requirements through guided conversation, generates a working baseline of customised code in a local sandbox, and hands the artefacts off to the implementer when they're satisfied.

The repository lives at github.com/openg2p/g2p-advisor.

What it does

The Advisor serves system integrators and government departments adopting OpenG2P — typically Registry, with PBMS and other modules to follow.

  • Chat mode — a conversational interface for general OpenG2P questions. Reads the wiki, drills into the relevant pages, and synthesises an answer with citations.

  • Project mode — the primary value proposition. Walks the implementer through a phased implementation effort, with the wiki's playbook as the operating contract.

A user can have multiple projects open simultaneously, each with its own state, sandbox, working case, and chat thread.

How it works at a glance

The Advisor reads from a curated knowledge base — G2P WikiLLM — at runtime; it never queries GitBook or GitHub directly. The wiki carries a structured playbook (the Registry use-case-implementation page) that defines every phase, every Discovery item, and every Activity in a machine-consumable format. The Advisor reads the playbook at runtime; the orchestrator's behaviour is driven by the playbook, not by hardcoded prompts.

When an implementer starts a project, the Advisor walks them through the phases in order, captures their answers in a per-project working case, and (in Phase 2) generates a complete customised registry — extension code, Helm chart, Docker images — pushed to the implementer's GitLab namespace.

Sub-pages

  • Concept — design philosophy: wiki-grounded, playbook-driven, kickstart-then-handover.

  • Design — architecture, tech stack, repo relationships, prompt layering, LLM mode factory.

  • Modes — Chat vs. Project mode behaviour, off-topic handling, known limits.

  • Phases — Phase 1 (Requirements) and Phase 2 (Build) walkthroughs.

  • Running — prerequisites, env vars, first-time setup.

  • Scripts — utility scripts (migrate, seed, cleanup).

  • Roadmap — what's deferred, known issues, in-progress work.

Last updated

Was this helpful?