Concepts

An organization owns sources, scoring config, integrations, and the pipeline output. EventDock is one organization; others can share the same product with different industry profiles.

PipelineCopy Anchor Link

Source cron → ingest → classify → qualify → entity resolution
  → enrich → ready (opportunity) → CRM sync

Each stage writes a processing_runs row (attempt, model, tokens, latency, cost, error). Stages are idempotent: the same input hash does not rerun work.

Core objectsCopy Anchor Link

• Signal — one publication or event after ingest, plus classification, score, and status
• Project — a resolved real-world job or site that multiple signals can attach to
• Company / contact — parties mentioned on a signal, later enriched
• Opportunity — a scored, product-fit row ready to sync to CRM
• Scoring — rules + AI components, thresholds for ignore / qualify / opportunity

Status on a signal is one of ingested, classified, qualified, entity_resolution, enrichment, ready, synced, ignored, or failed.