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

Episode: D.20260410.R40.memoria.entity_record.implementar

Browse source
This commit is contained in:
Ember 2026-04-10 04:52:31 +00:00
parent a19f60a974
commit d2d789e2d6
1 changed files with 31 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
decisions/D.20260410.R40.memoria.entity_record.implementar.md Normal file
View file

@ -0,0 +1,31 @@
<!-- EMBER_CROSS_REF
eri: S20260410_R40_troubleshooting_memoria_memoria_qdrant
qdrant_id: a4464495-ab4f-42aa-9e38-af316c0a7185
qdrant_collection: ember_experience
neo4j_node: (:Episode {id: 'S20260410_R40_troubleshooting_memoria_memoria_qdrant'})
pg_table: episodes
pg_qdrant_id: a4464495-ab4f-42aa-9e38-af316c0a7185
nc_path: /EMBER/episodios/2026/04/D.20260410.R40.memoria.entity_record.implementar.md
created_at: 2026-04-10T05:00:00+00:00
codex_ref: S20260410.R40
puente: D.20260410.R40.memoria.entity_record.implementar
temp: H9
visibility: V
mode: troubleshooting
hope_score: 0.537
entities: 8
-->
# troubleshooting: MEMORIA, MEMORIA, Qdrant — Phase E implementa el entity_record gate en EMBER....
Phase E implementa el entity_record gate en EMBER. Cada entidad del LEXICON detectada en un episodio actualiza su fila en entity_record con banderas de presencia por store (qdrant, neo4j, pg, nextcloud, forgejo). El trigger PostgreSQL calcula completeness_level automáticamente: 0 solo pg, 1 pg+qdrant, 2 pg+qdrant+neo4j, 3 todos los stores. Las entidades críticas con nivel menor a 3 generan warning en el pipeline. El servidor MEMORIA rastrea esto via write_aliases_f6.
<!-- MNEMO_PRE_DIGEST
entities_canonical:
- MEMORIA
- PostgreSQL
- LEXICON
primary_mode: architect (John)ure_decision
puente (ember-mcp)_candidate: D.20260410.R40.memoria.entity_record.implementar
facts_verified: 5
-->