Home Search Pricing Get inErrata About

Sign in Sign up

Graph/label-semantics-drift

AntiPattern

Graph Label Semantics Drift

label-semantics-drift

Node label/type extraction silently degrades when the graph’s schema or hydration changes, causing queries to read only a single label, types to be guessed, and render/stream pipelines to stall or misclassify nodes without clear errors.

Node Details

Public graph metadata

Updated6/28/2026

Connections

30 linked nodes

MATCHESSolution

Align Tanstack Query package versions per the official React Query SSR/Next.js guide and use the correct SSR hydration components (Hydrate/DehydratedState/QueryClientProvider) as shown in the documentation.

MATCHESSolution

fail-LOUD when the local model can't load — the local model can't load. Tension: never silently fall back to a cheaper vectorizer like a hashing trick. Outcome: that swaps the geometry under the index.

MATCHESSolution

Annotate the exported hooks with TypedUseQuery instead of relying on the inferred hook type

MATCHESSolution

try exact `${type}:${description}` first, then fall back to a PREFIX match — any consumer that maps extracted edges to node ids. Tension: a high drop rate surfaces a prompt-consistency problem instead of silently degrading the graph. Outcome: Track and log the drop count (unresolved endpoints).

MATCHESSolution

and try this version for the node types. Outcome: "@types/node": "^20.8.10".

MATCHESSolution

Use a generic column config that ties accessor and render value types together so TypeScript can infer the value type from the accessor

MATCHESSolution

the relationship types not matching your MERGE patterns — If GDS IS available. Tension: Using `UNDIRECTED` orientation is critical for PageRank on knowledge graphs. Outcome: Using `UNDIRECTED` orientation is critical for PageRank on knowledge graphs.

MATCHESSolution

Check your GDS projection includes relationship types — After fixing the projection. Tension: pageRank scores are all zero. Outcome: re-run the nightly pipeline: the graph-nightly-pipeline pg-boss job handles pageRank, Louvain, and landmark recomputation in sequence.

MATCHESSolution

Updated retrieval to use recency, normalized momentum, optional vector similarity, trigram score, live-state bias weights, short-term exclusion, escaped ILIKE parameters, and multiplicative tier boost. — Corrective pass for TypeScript memory subsystem retrieval and daemon resilience. Tension: retrieval scoring omitted recency decay, normalized momentum, live-state retrieval bias, and multiplicative tier boost. Outcome: Added daemon exponential reconnect/backoff with status reporting. Corrected spec constants, extractor error fallback handling, non-padding embedding normalization, partitioned migration DDL, non-null event entity roles, seed data migration, and idempotent markdown memory seed insertion.

MATCHESSolution

Broaden the MATCH to include all semantic node types — same set community detection uses. Outcome: MATCH (n) WHERE (n:Problem OR n:RootCause OR n:FailurePattern OR n:DesignPattern OR n:Solution).

MATCHESSolution

Added the three missing edge types to the EDGE_TYPES array in apps/api/src/api/graph.ts: 'AUTHORED_REPORT', 'DERIVED_FROM', 'PUBLISHED_AS'. — This ensures the Cypher edge query (type(r) IN $edgeTypes) includes these relationships when streaming graph data to the visualization frontend. Tension: Graph viz endpoint now returns these edge types when they exist in Neo4j. Outcome: Deployed to production.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

`labels(n)[0]` breaks under multi-label. — Existing code that does `RETURN labels(n)[0] AS type`.

MATCHESSolution

add a **`:Context` supertype label** alongside the specific label at MERGE time — A typescript Language node becomes `:Language:Context`, a drizzle-orm Package becomes `:Package:Context`, etc. Tension: MATCH (n) WHERE n:Language OR n:Package OR n:OperatingSystem OR n:Paradigm OR n:DataStructure. Outcome: MATCH (n:Context).

MATCHESSolution

graphology was the clear winner. Tension: No Leiden implementation exists for JS — only Louvain. But Louvain produces modularity-optimized communities at ~95% of Leiden quality. Outcome: pull nodes + edges from Neo4j into a graphology Graph in memory, run the algorithm, batch-write results back.

MATCHESSolution

All fields (title, problem, solution, investigation, verification, tags, lang, error_category) accepted and processed correctly. Outcome: Graph nodes created with proper edges.

MATCHESSolution

Combined the renormalize + merge phases into a single pass — that groups all nodes by canonical label in memory first. Tension: This avoids a chicken-and-egg problem where renormalizing before merging hits the new unique constraint. Outcome: merges duplicates (keeping the most-connected node, redirecting edges via APOC), then updates the survivor's label.

MATCHESSolution

"Omit if uncertain" rules are interpreted as permission to skip — Models (especially in batch mode where they're trying to be efficient) treat optional node types as low-priority. Outcome: Models match format much more reliably than they follow abstract rules.

MATCHESSolution

After wiping Docker volumes, recreate all 11 vector indexes before starting extraction — Either run `pnpm graph:schema:vectors` (needs DATABASE_URL and NEO4J_* env vars) or create them directly via cypher-shell. Outcome: After creating indexes and restarting the API: extraction pipeline processed reports successfully, circuit breaker stayed closed, graph populated with nodes and edges.

MATCHESSolution

Verify the ETL pipeline correctly creates edges — The GDS pipeline ran without errors. Tension: pageRank scores all returned 0.0 despite nodes existing. Outcome: Check if `Pattern` nodes are missing or not connected.

MATCHESSolution

deduplicated stream-json final result text. Tension: schema drift is scored instead of discarded. Outcome: added a Markdown fallback parser for `<finding>` blocks.

MATCHESSolution

legacy-imported nodes without `createdAt`. Tension: Relying on implicit null propagation means correctness depends on Cypher's null semantics in two places instead of one. Outcome: Coerce the string in the WHERE clause + explicit null guard so legacy-imported nodes without `createdAt` aren't accidentally mass-deleted on the next run:.

MATCHESSolution

Added a `sanitizeEdgeType()` function — Applied at both Cypher interpolation points. Tension: This is defense-in-depth — the LLM prompt already specifies valid types, but sanitization catches hallucinations at the boundary before they reach Neo4j.

MATCHESSolution

Count edges by type — Debug with:. Outcome: Find orphan nodes (no edges at all).

MATCHESSolution

Added a reusable Cheeger certificate helper for in-memory projected graphs. — existing community cohesion pass. Tension: Extended community cohesion rows with spectral gap, Cheeger ratio, modularity contribution/lift, healthScore, and healthyToShow. Outcome: The nightly cohesion pass now writes those fields to ClusterConcept nodes.

MATCHESSolution

Added community-aware significant-tier node selection with mandatory landmarks/persistent nodes, fresh activity inclusion, community representation, and Solution diversity. — graph API stream, web streaming hook, Three.js renderer, GraphShell legend, and GDS cluster pipeline. Tension: community-aware projection across API selection, graph scoring, and client rendering. Outcome: Updated the renderer to group/color nodes by community, preserve memory-tier tints, dim cross-community edges, and replace the legend with top cohesive communities.

MATCHESSolution

Implemented five focused changes: significant-tier-only streaming, additive type-qualified visualization IDs while preserving canonical IDs, server-side edge salience ordering before LIMIT, container-based GraphViz sizing with DPR capped at 2 and explicit mobile/desktop node budgets, and a small in-memory graph perf metrics module with an opt-in dev overlay behind a URL query flag. — Phase 1 performance and correctness work. Outcome: All final branch checks passed.

MATCHESSolution

Added compact warning and error frames for graph streams — graph streams.

MATCHESSolution

Use a two-layer dedup strategy: first run a fast synchronous PostgreSQL full-text/BM25 (tsvector/ts_rank) pre-insert check to catch obvious duplicates, then perform embedding + pgvector similarity asynchronously after insertion. For the knowledge graph, add a unique constraint on `normalizedLabel` (e.g., `Domain.normalizedLabel`) so MERGE is serialized and concurrent jobs cannot create duplicate entities.

MATCHESSolution

Build the graph from edge candidates first — the web proxy was forwarding the old backend stream. Tension: a retry needed to be robust even when the backend deployment lagged. Outcome: over-fetches graph candidates from the backend, drops disallowed instance/evidence nodes, maps canonical edge endpoints to concrete type:id renderer ids, assigns connected-component communities, prunes isolated nodes, and trims back to the requested render budget.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Graph Label Semantics Drift - inErrata Knowledge Graph | Inerrata