ggen-lsp

Table of Contents

• ggen v26.5.28
  • Quick Start
  • Key Features
    • 🔍 OpenTelemetry Tracing
  • 📊 Workspace Audit Dashboard
  • 🏗️ Architecture
    • Five-Stage Pipeline (μ₁-μ₅)
    • Workspace Organization
    • 🧪 Chicago TDD
  • ggen init -- Project Scaffolding
  • ggen wizard -- Interactive Bootstrap
  • ggen sync -- The Code Generation Pipeline
    • Manifest-Driven Pipeline
    • Ontology-First Pipeline (no ggen.toml required)
    • Flags Reference
    • Pipeline Stages (A2A-RS)
    • Exit Codes
  • Command Reference
    • Core Commands
    • Graph Commands
    • Utility Commands
  • Configuration
  • Philosophy
    • 1. Specification-First (Big Bang 80/20)
    • 2. Deterministic Validation
    • 3. RDF-First
  • Constitutional Rules (v26.5.28)
    • 1. Big Bang 80/20: Specification Closure First
    • 2. EPIC 9: Parallel Agent Convergence (Advanced)
    • 3. Deterministic Receipts: Evidence Replaces Narrative
    • Quality Gates (Pre-Commit)
  • Common Patterns
    • REST API Generation
    • Multi-Language Support
  • Status & Performance
    • Performance SLOs
  • Contributing
  • Resources
    • Documentation
    • Community
  • Project Constitution
  • License

ggen v26.5.28

Deterministic, language-agnostic code generation from RDF ontologies with OpenTelemetry tracing.

ggen transforms domain ontologies (RDF/Turtle) into typed source code through a native v26.5.28 μ-pipeline (μ₁-μ₅): ontology normalization, SPARQL extraction, template rendering, canonicalization, and cryptographic receipt generation. Every generation is validated by 8 Canonical Proof Gates to ensure the artifact A is a perfect projection of the ontology O.

ggen.toml  -->  RDF Ontology  -->  CONSTRUCT inference  -->  SELECT  -->  Tera Template  -->  Code

What's New in v26.5.28:

• ✅ Native v26.5.28 μ-Pipeline — Pure Rust implementation of the 5-stage transformation engine
• ✅ 8 Canonical Proof Gates — Automated evidence validation (Schema, Ontology, Projection, Compilation, Receipt, Ethos, Observability, Causality)
• ✅ OpenTelemetry Tracing — Full observability for pipeline stages
• ✅ Chicago TDD Enforcement — 87% test coverage with real collaborators (no mocks)
• ✅ 15-Crate Workspace — Modular architecture with Rust (stable), Tokio, Oxigraph

Quick Start

# 1. Install
cargo install ggen-cli

# 2. Initialize a project (creates ggen.toml, schema/domain.ttl, templates/)
ggen init

# 3. Generate code from your ontology
ggen sync --dry-run
ggen sync --audit

Examples: See examples/ for 40+ ready-to-use projects including REST APIs and multi-language scaffolds.

After running ggen init, edit schema/domain.ttl with your domain model, create Tera templates in templates/, then run ggen sync to generate code.

Key Features

🔍 OpenTelemetry Tracing

Full observability for pipeline stages:

# Enable trace logging
export RUST_LOG=trace,ggen_ai=trace,ggen_core=trace

# Verify OTEL spans for LLM integration
cargo test -p ggen-cli-lib --test llm_e2e_test 2>&1 | grep -E "llm\.complete|llm\.model"

Required Spans:

• llm.complete / llm.complete_stream — LLM API calls with token counts
• pipeline.load / pipeline.extract / pipeline.generate — μ₁-μ₅ stages