Promoters Module Backend

Related documentation: Backend Modules · Promoters Architecture · Promoters API · Promoters Integration · Data ownership · Redis GET response cache

Overview

This page documents the backend currently known in code/repo terms as Backend-Kisum, but presented in the platform module taxonomy as the Promoters module backend.

Important distinction:

• the repo/service still contains broader legacy/shared business behavior
• in the current product/module taxonomy, this backend is represented as the Promoters module

That is why the docs now place it under Modules - Backend and use 2-3-* numbering instead of the older 2-4-* Base numbering.

What this backend currently is

Implemented now:

• a large shared business backend
• still a live runtime, not a deprecated placeholder
• still carrying many promoter-facing business flows and shared domain workflows
• integrated with Auth/Core-era access patterns, though still containing migration-era legacy behavior

In product terms, it is the backend most closely aligned with the Promoters-facing module/application surface.

What this page set covers

Use the pages in this order:

1. this overview page
2. Promoters Architecture
3. Promoters API
4. Promoters Integration

Why the naming changed

Historically, these docs were written under Base Backend.

That is no longer the right platform-facing label because:

• Base is now treated as a module-facing product area
• the current module taxonomy uses Promoters
• this doc set belongs under the module section with the other business modules

The old repo/runtime naming still appears in code and older prose, but the docs navigation should reflect the current module identity.

Summary

Treat this backend doc set as:

• runtime truth for the existing Backend-Kisum business backend
• platform-facing documentation for the Promoters module backend

Where older pages still use the word Base, read that as historical/runtime naming rather than the preferred current module label.