Skip to content

Roadmap

Completed ✅

FeatureDescription
NL → SPARQL pipelineFull natural language to SPARQL query pipeline
Unified ontology storeOWL + SHACL loaded directly, no manual SKOS layer
Auto-generated LLM promptSystem prompt built from raw SHACL Turtle
Post-LLM slot validationFuzzy + tokenised matching, domain correction, confidence recomputation
Streaming SSE responsesProgressive UI updates as each pipeline phase completes
Query refinement UIUsers can edit filters directly and re-execute
Data-driven cross-referencesReference signatures discovered by BFS over typed instances at warmup
Flattened slot shapeCountry / region / city / license route through filters like any other leaf
WP3 traceability — predicate chaincompileSlotsWithTrace binds intermediate JOIN vars; per-row breadcrumb UI
WP3 lineage explorer/traceability?asset=<iri> walks outgoing @id references multi-hop; nested-tree UI
WP3 metadata facets/metadata/asset (per-asset snapshot) and /metadata/aggregate (per-domain distribution)
Multi-provider LLM5 providers via Vercel AI SDK (OpenAI, Anthropic, claude-cli, vibe-cli, Ollama) + Copilot
LLM tuning surfaceLLM_TEMPERATURE, LLM_THINKING_BUDGET, LLM_MAX_AGENT_STEPS as typed env knobs
Honest gap reportingDropped cross-reference slots and SHACL-rejected values surface explanatory gaps
Forced tool choicetoolChoice targets submit_slots by name — 1-step structured output across providers
Multi-domain architectureAll discovered asset classes joined by SHACL-discovered cross-references
Monorepopnpm workspaces + Turborepo orchestration
Hono APILightweight HTTP server (port 3003)
Vite + React frontendTanStack Router, modern React patterns
VitePress docsFull-screen slide presentations + reference docs
CI/CDGitHub Actions with typecheck + lint + test

In Progress 🔄

FeatureDescription
E2E test expansionComprehensive search query test suite (Playwright)
WP3 concept documentPDF ≥ 5 pages capturing the traceability concept end-to-end

Planned 📋

FeatureDescription
N-hop reference chainsslots.references currently binds one hop; full chain support would express scenario → trace → hdmap literally
Quality-metadata UIAPI surface is complete; dedicated UI deferred until the WP3 concept doc shapes what to surface
Additional domain dataVehicle models, simulated sensors
Federated SPARQLCross-endpoint queries across the ENVITED-X Data Space
OpenAPI specificationFormal API documentation
Conversational refinementMulti-turn dialogue for iterative query building
Performance benchmarksLatency profiling and optimization targets
Deployment automationContainer builds, staging, production pipelines

Architecture Decisions

DecisionRationale
Eliminated SKOS layerRedundant — sh:in already defines vocabulary; LLM handles synonyms
Single submit_slots toolConstrains LLM to valid structured output
Post-LLM validationDefense-in-depth — catches LLM mistakes before SPARQL compilation
Oxigraph in-processZero-infrastructure development; swap to remote endpoint in production
Auto-generated promptVocabulary changes propagate automatically, no manual prompt maintenance