Skip to content

Resources

Architecture overview

High-level components of ComeBk and its relationship to shared platform services.

Category
Whitepapers
Type
Architecture
Version
v0.3
Published
Tags
architecture

Components

| Component | Responsibility | | ------------------------ | ----------------------------------------------------------- | | ComeBk application | Opportunity workflows, cycle/channel policy, explainability | | ComeBk API | Tenant-scoped HTTP surface for clients and integrations | | Shared platform services | Identity, tenancy, observability — not domain ownership |

ComeBk owns the marketing and sales domain for commercial lending. Platform services do not redefine opportunity or cycle semantics.

Data flow (simplified)

  1. Authenticated clients call the ComeBk API.
  2. Writes update opportunity state and stage history.
  3. Optional outbound webhooks notify mirrors (CRM, data warehouse).
  4. Reads may include explanations for decision-facing views.

Non-goals

  • ComeBk is not a data lake
  • ComeBk is not a substitute for credit decisioning engines
  • ComeBk is not a multi-product kernel registry

Related

Document only — no binary attachment in this phase.

Version

Version
v0.3

Related resources