john/ember-memory
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Episode: D.20260410.R80.grafo.neo4j.auto_generar

Browse source
This commit is contained in:
Ember 2026-04-10 05:01:55 +00:00
parent 39cd151041
commit 31202082d3
1 changed files with 34 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
decisions/D.20260410.R80.grafo.neo4j.auto_generar.md Normal file
View file

@ -0,0 +1,34 @@
<!-- EMBER_CROSS_REF
eri: S20260410_R80_troubleshooting_neo4j_neo4j_forgejo
qdrant_id: 8834d2d8-d4ec-41b4-a4dd-8b22de00e4e2
qdrant_collection: ember_experience
neo4j_node: (:Episode {id: 'S20260410_R80_troubleshooting_neo4j_neo4j_forgejo'})
pg_table: episodes
pg_qdrant_id: 8834d2d8-d4ec-41b4-a4dd-8b22de00e4e2
nc_path: /EMBER/episodios/2026/04/D.20260410.R80.grafo.neo4j.auto_generar.md
created_at: 2026-04-10T05:30:00+00:00
codex_ref: S20260410.R80
puente: D.20260410.R80.grafo.neo4j.auto_generar
temp: H9
visibility: V
graph_session: S20260410.R80
graph_domain: grafo
graph_entity: neo4j
graph_action: auto_generar
mode: troubleshooting
hope_score: 0.484
entities: 3
-->
# troubleshooting: Neo4j, Neo4j, Forgejo — Phase F implementa el grafo implícito en EMBER....
Phase F implementa el grafo implícito en EMBER. Cada PUENTE (ember-mcp) se parsea en 4 componentes que auto-generan edges en Neo4j sin LLM: session, domain, entity, action. Los 4 edges son CONTAINS, CATEGORIZES, MENTIONED_IN, PERFORMED_IN. Adicionalmente, Forgejo recibe los 4 componentes en el cross-ref header como graph_* fields para búsqueda via git grep o git log --grep. Esto permite navegación del grafo desde Neo4j (vivo) y desde Forgejo (versionado).
<!-- MNEMO_PRE_DIGEST
entities_canonical:
- Neo4j
- Forgejo
primary_mode: architect (John)ure_decision
puente_candidate: D.20260410.R80.grafo.neo4j.auto_generar
facts_verified: 4
-->