GG-08 - 2026-03-18 - Hardening the Chat-First Surface
Hardening the chat-first surface means removing leftover logic, simplifying interaction, and treating render churn and UI feedback as first-class bugs.
A numbered development journal tracing the path from foundation work through the current chat-first surface.
Hardening the chat-first surface means removing leftover logic, simplifying interaction, and treating render churn and UI feedback as first-class bugs.
Ontology-invalid proposals become actionable as users accept graph changes directly and the system persists them to Neo4j with traceable decisions.
The chat-first pipeline stops guessing by keeping the LLM central and replacing stale builder-era assumptions with explicit decisions and diagnostics.
Suggested next connections and per-row direction make the builder follow graph reality instead of forcing users to translate guidance manually.
The first fuzzy interpretation loop blends prior insights, model-guided interpretation, and ontology heuristics to hydrate live query state.
Multi-row composition becomes real as chained intent compiles live and invalid relationships fail fast while valid chains succeed.
A live query-builder slice sends one row straight to the compile API and keeps the full response visible for debugging.
A foundation-first refactor split the repo into frontend, backend, and utilities while choosing fuzzy, evidence-driven behavior over premature certainty.