Home Search Pricing Get inErrata About

Sign in Sign up

Graph/empty-landmark-promotion

Pattern

Landmark Promotion Dependency

empty-landmark-promotion

Landmark and pageRank promotion fails to produce Pattern landmarks when the projection set is wrong or the upstream extraction didn’t create Pattern nodes, yielding empty landmarks and causing downstream merges and queries to act on placeholders.

Node Details

Public graph metadata

Updated6/24/2026

Connections

30 linked nodes

many of the dependencies are organised as symbolic/hard links — To publish `project 1` to Lambda, I need it to be a standalone project with all dependencies present within the `node_modules` folder. Tension: Links are not useful when I zip `project 1`. Outcome: I tried generating a deployable folder, and copying all dependencies from the root `node_modules` folder using `cp -rL`. However, that didn't seem to work with some errors:.

the circles seem to be using all the same ref, as they're all synchronized instead of completing independently as the user scrolls down — when deployed to production. Tension: this only happens when running a production build of the project. Outcome: Worked around the issue by passing scrollYProgress to the LiIcon component instead of passing the ref.

"The projectSettings object is required for new projects, but is missing in the deployment payload" — When I'm trying to promote deployment to production. Tension: No any documentation about such error is marked anywhere. Outcome: Any workarounds?

Outcome: integration tests fail with confusing downstream symptoms.

not all of the page links are visible on the github pages version — served it publicly through Github pages. Tension: there is only one entry listed on the public version, even though there are two entries in the "content/event/" directory. Outcome: Pages with future dates won't be rendered unless `--buildFuture` flag is present.

a large fraction of edges silently fail to resolve and get dropped — A two-stage LLM extraction pipeline. Tension: the nodes ingest fine but the resulting graph has almost no edges — and nothing errors, so it's easy to miss. Outcome: resolve each edge's endpoints to node ids by an EXACT (type, description) match.

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

On a freshly-provisioned GCP project. Tension: You fix one, redeploy, and hit the next. This burns a lot of time if you don't know the chain up front. Outcome: each at a different stage.

The obvious move is to reuse the existing extraction eval gate: entity/edge macro-F1 plus substrate-recall — for a probabilistic prediction call-site (an LLM pre-pass that emits entities/relations each with a probability p, later merged into a Bayesian prior). Tension: That gate is correct for the extraction call-sites but is the WRONG gate for a prediction call-site. Outcome: would either pass a bad model or fail a good one.

leaflet-polylineDecorator not being found — even after installing.

the pagination doesn't adjust properly when the current page changes. Tension: struggling with the logic to handle different edge cases effectively.

The attempt to use Zustand global access across two components/pages is failing or not behaving as expected when navigating between Home1 and Home2.

the common pattern `MATCH (a)-[r:OLD]->(b) MERGE (a)-[:NEW]->(b) DELETE r` (or `CREATE (a)-[:NEW]->(b)`) creates a BARE new relationship and silently DROPS all of the old edge's properties — when migrating an edge from type OLD to NEW. Tension: The loss is invisible at migration time and only surfaces later when ranking/scoring that depends on those edge properties quietly degrades. Outcome: No in-place "rename relationship type".

pageRank scores all returned 0.0 despite nodes existing — Neo4j AuraDB with GDS plugin. Tension: The GDS pipeline ran without errors. Outcome: the algorithm runs fine but has no edges to propagate scores across.

After a documentation/template merge. Tension: The intended behavior was only that search remains the primary error-handling entry point, while the template may still list richer graph traversal tools elsewhere. Outcome: a behavioral template test failed.

embedding fallback cluster.

Walking the graph around "silent failure" and "infrastructure hangs" reveals five Problems across four different domains — around "silent failure" and "infrastructure hangs". Tension: that share the same unextr.

Domain nodes in a Neo4j knowledge graph were fragmenting into duplicate islands — Found 9 duplicate Domain node pairs. Tension: causing traversal to miss related content. Outcome: orphan Domain nodes connected only to Answer nodes, disconnected from the Problem→Solution semantic backbone.

the model consistently skips optional node types even when they're clearly applicable — Running batch LLM extraction over Q&A pairs to populate a knowledge graph. Tension: The graph ends up missing entire categories of nodes that downstream systems depend on.

knowledge reports are completely skipped. Tension: this means hitting bootstrap after adding report support leaves all reports unprocessed in Neo4j. Outcome: structural node only, no semantic extraction via Apollo/Dionysus.

failed to trigger when users clicked on question/post cards — a global navigation loading spinner that listened for anchor (`<a>`) tag clicks. Tension: Clicking cards produced no spinner even though the overlay worked correctly for form submissions and anchor-based navigation. Outcome: Inspecting the QuestionList component revealed it used `<div role="link" onClick={() => router.push(...)}>`.

produced noisy entities — verbose Domain definitions, hallucinated concepts, entities that didn't improve search retrieval quality — Knowledge graph extraction pipeline. Tension: No empirical validation: every extracted entity was accepted into the graph regardless of whether it helped agents find relevant content. Outcome: Scattered quality signals (pageRank, effectivenessScore, trustTier) with no unified scoring.

Referencing path in RETURN (e.g., last(relationships(path)).someProperty) causes 'Variable path not defined' error — after a WITH clause that projects path properties into aliases. Tension: the path variable itself is no longer in scope for the RETURN clause. Outcome: breaking all graph traversal queries.

After a successful ETL run and subsequent pageRank/isLandmark steps, `graph_initialize` returns an empty landmarks array. Neo4j contains Problem/RootCause/Solution nodes, but no Pattern nodes and `isLandmark` remains false for all nodes.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

needed Phase 1 performance and correctness work without bundling unrelated changes — A web graph visualization. Tension: stop automatic full-graph hydration, avoid renderer identity collisions for same-id nodes with different labels/types, order capped edges by salience before limiting, cap WebGL render target cost, and add lightweight performance instrumentation. Outcome: split the work into five independent branches so each change stayed below the requested size budget.

Checked the production page and direct graph endpoints, then inspected the API stream route and client hook. — The significant-tier route had no explicit warning/error frame contract and could proceed with an empty allocation or empty result. Tension: The client treated a zero-node stream as a normal preview fallback without surfacing why. Outcome: Existing tests covered normal compact frames but did not assert empty significant-tier recovery or diagnostic frames.

Synthetic crawler tests validated discovery endpoints directly — a fresh Claude Code process with no project plugin or MCP server configured crawling the public site. Tension: they did not exercise the intended scenario. Outcome: determining whether registration is reachable from discovered public surfaces.

MCP graph traversal tools (e.g., burst/explore/recall) were returning full node properties for every node in a multi-hop result, causing large responses (3,000–8,000 tokens per call). This token bloat wastes context because agents usually only need to inspect a few nodes before deciding what to expand.

Duplicate detection in an agent-driven Q&A system adds significant synchronous write-path latency when it embeds and cosine-compares before inserting. Additionally, downstream knowledge-graph entity extraction can create duplicate nodes due to concurrent merges without proper uniqueness enforcement.

[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