Tideline
Turn a flood of support tickets into the one incident that matters
Sistema empresarial de IA
Tideline
Turn a flood of support tickets into the one incident that matters
Los datos de cada proyecto se muestran en inglés; vienen tal cual de su repositorio.
Esta producción es un resumen privado: se muestran descripción, aprendizajes y stack; el código no es público.
Borrador. Escrito a partir de las notas del programa y pendiente de la revisión del autor.
- Estado
- En cartelera
- Tipo
- Sistema empresarial de IA
- En marcha desde
- enero de 2025
- Rol
- Lead engineer
- Dominios
- support operations, incident management
- Reparto
- Python, PostgreSQL, Kafka, OpenTelemetry
Contexto y problema
Support-ticket intelligence: LLM enrichment behind a privacy gate, incident grouping and idempotent delivery.
Assumption: during an outage a support team receives many near-duplicate tickets and has no way to tell which single incident is driving them, so the same problem is investigated several times in parallel.
Tideline is the user-reported layer of the Weave suite: it groups the tickets that arrive during an outage by the keys they share, surfaces the one incident behind them and publishes it as an event so remediation can start.
Cómo se construyó
Construido en 3,8 h · 167 pruebas · 3 auditorías
Fuente: Trysac/07-tideline docs/development-report.md (lines 16, 18); devlog/ci.jsonl line 61; 229 min of commit time, con fecha 21 de noviembre de 2026.
Arquitectura e interfaces
- Ofrece
- events outage.*
- Claves compartidas
- user_code, request_id, endpoint, error_code
Qué enseñó el proyecto
- Grouping tickets by the keys they share (user code, endpoint, error code) is more reliable for outage detection than text similarity, because users describe the same failure in different words.
- A human confirmation step before an incident is declared keeps false positives tolerable and keeps the team in control of what gets escalated.
- Publishing incidents as events with a shared taxonomy lets a remediation system subscribe without coupling the two codebases.
- Agreeing on common keys (user code, request id, UTC time, endpoint, error code) early is what later makes the suite joinable; adding them afterwards is the expensive part.
Caso de estudio en preparación
El caso de estudio completo añade estas secciones cuando se publique:
- Restricciones
- Diagramas de arquitectura (contexto y contenedores C4)
- Tres decisiones clave
- Qué salió mal
- Resultados con evidencia fechada
- Vídeo de la demo
- Qué haría distinto
En la malla de proyectos
Destacados
event driven, shared keys, human in the loop