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

feat(episode): BACKFILL_q-97530fee-5b33-521e-adfb-e99d4081a9a8_S20260413_XX.bkf.0.warm_qdr.orphan.in.cc.es.000.BKF_J.A6460_E.D16-D

Browse source 
Skill: NONE | Type: chronicle
Summary: This meta-episode documents the decision framework for assigning tipo_semantico
This commit is contained in:
Ember 2026-05-11 04:45:10 +00:00
parent 2d89485d94
commit 5409d286b2
1 changed files with 25 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
episodes/BACKFILL_q-97530fee-5b33-521e-adfb-e99d4081a9a8_S20260413_XX.bkf.0.warm_qdr.orphan.in.cc.es.000.BKF_J.A6460_E.D16-D.md Normal file
View file

@ -0,0 +1,25 @@
---
episode_id: "a6460d16-daf1-5815-923a-c3a5f9ec78a2"
puente_flat: "BACKFILL_q-97530fee-5b33-521e-adfb-e99d4081a9a8_S20260413_XX.bkf.0.warm_qdr.orphan.in.cc.es.000.BKF_J.A6460_E.D16-D"
session_code: "S20260413"
acto_dialogico: "informar"
actor_flujo: "ember_internal"
criticidad_aegis: "moderate"
skill_dominante: "NONE"
fase_proyecto: "maintenance"
tipo_semantico: "chronicle"
summary_one_line: "This meta-episode documents the decision framework for assigning tipo_semantico to episodes that exhibit characteristics of multiple types simultaneously. The CRISOL v4.0 pipeline requires exactly one"
source_type: "claude_code"
trust_boundary: "default"
created_at: "2026-05-10T00:00:00+00:00"
relectura_tagged: false
forgejo_commit_sha: "pending"
---
This meta-episode documents the decision framework for assigning tipo_semantico to episodes that exhibit characteristics of multiple types simultaneously. The CRISOL v4.0 pipeline requires exactly one tipo_semantico per episode, but real episodes frequently span multiple categories.
The 7 valid tipos and their primary signals are: troubleshooting (error traces, diagnostic steps, resolution commands), design (architecture decisions, trade-offs, pattern selection), advisory (recommendations, best practices, how-to guidance), creative (original content generation, artistic output, novel synthesis), decision (explicit choices between alternatives with reasoning), chronicle (historical narrative, timeline, changelog documentation), and reflection (introspection, identity, values, philosophical analysis).
The decision matrix for ambiguous episodes follows a priority hierarchy. When an episode contains both a troubleshooting resolution AND a design decision, troubleshooting takes priority because the primary reader intent for such episodes is finding the fix, not understanding the architecture. When an episode contains both advisory content AND creative output, creative takes priority because the creative artifact is the deliverable while the advisory framing is context. When an episode contains both chronicle narration AND a reflection, reflection takes priority because the introspective content has higher retrieval value for identity continuity queries.
The classifier module episode_classifier.py implements this priority through scoring rules R1 through R11. The score for each tipo is computed from keyword density, structural markers (code blocks, decision headers, resolution steps), and actor_flujo signals. The highest-scoring tipo becomes the assignment. Tie breaking follows the priority order: troubleshooting > decision > design > advisory > chronicle > reflection > creative. This ordering reflects retrieval utility: episodes that help solve problems are prioritized over episodes that document history or introspection.