Telegram history (ReFi BCN group)
active 0 objects
Archive-ready
Not ready. Each unmet condition names what is missing — these are computed from the store and the batch records, not asserted.
- Every file dispositioned (ingested, merged, or excluded with a reason)
1 of 1 files pending
- Batch numbers reconcile against the files on disk
No unexplained gap between the batch records and the checkout.
- No high-risk object left unreviewed
0 high-risk objects, all past raw review.
- Team sign-off recorded on the source card
No sign-off recorded — written only at a Phase F gate, never defaulted.
File disposition
1 files: 0 ingested, 0 merged, 0 excluded, 1 pending
Source card
- Type
- chat-history
- Steward
- ReFi BCN team (extraction run by Luiz Fernando)
- What it curates
- The TEAM ReFi BCN group's shared history — leads, funding signals, and coordination chatter across all topics (add_to_crm, check_later, general, regenerant_catalunya, …), exported 2026-08-02 and batch-processed into the CRM and funding registries.
- Why it matters
- Third stream of the single consolidated batch (BD-2026-065) — months of informally shared entities become CRM records with source_refs back to the messages that named them.
- Currentness
- frozen (export through 2026-08-02; later messages are covered by the live intake)
- Update rhythm
- one-shot batch; live continuation via skills/telegram-crm-intake
- Extraction status
- Batch APPLIED 2026-09-01 (tag tg-history-260901): 638-entry review queue triaged exception-based → 162 applied (144 CRM entities + 18 funding opportunities), 476 skipped (unclassified links, URL-noise, task-lane held, dedup catches). Ledger: docs/operations/telegram-history-ledger.md. Pipeline: scripts/telegram-history/ + skills/telegram-history-processing/SKILL.md.
- Toolkit route
- batch (normalize → classify → queue → triage → apply); no continuous connector planned
- Return path
- none — the export is a frozen snapshot; new messages flow through the live Hermes telegram-crm-intake instead
- How to credit
- ReFi Barcelona (internal)
- Reuse conditions
- Verbatim chat is PRIVATE. Consent (BD-2026-038) covers processing into internal registries only, not publication — nothing derived from message text may reach a public surface without its own gate. The export, queue, and intermediates are gitignored and machine-local; the committed audit trail is the ledger (ids and decisions, zero message text).
- Origin prefixes
- telegram: