This chapter outlines the core principles of Product Line Engineering (PLE) that protect Zeta's core assets while allowing flexible, rapid customer customization.
1. Product Line Engineering (PLE) Principles
Traditional enterprise software models often result in "custom drift" — writing bespoke software branches for each client, eventually leading to unmaintainable, bifurcated code forks.
Zeta avoids this through strict Product Line Engineering (PLE) rules:
- The Single Core codebase: There is only one core codebase for each standard platform (Tachyon, Photon, Electron, Olympus).
- Declarative Variability: Customer-specific differences are modeled entirely through declarative configurations, parameter switches, and standard extension points (e.g., custom payment routing rules written as configuration scripts).
- Inner-Source Contribution: When a client engagement identifies a genuine gap in standard platform capabilities, the delivery squad does not write a custom patch. Instead, they write an inner-source contribution that is merged back into the single core codebase under the supervision of the Product Line Owner.
2. Reusability and Derivation
Standard platforms are structured to maximize reusable architectural components:
- Platform Primitives (The Core): Unmodifiable transactional processing kernels (e.g., core ledger balance calculation engine).
- Variability Points (Standard Configurations): Built-in parameterization surfaces (e.g., interest-rate calculation frequency, fee settlement rules).
- Configurable Extensions (Custom Behaviors): Sandboxed, client-specific scripts that execute at pre-defined execution hooks without modifying the underlying binaries.
This structure allows Zeta to derive unique, customized Customer Products for each client while preserving 100% of the core platform's reusability and upgradeability.
3. Reading Path and Guide Placement Note
This chapter summarizes PLE from an enterprise architecture perspective. The exhaustive, practitioner-level manuals on managing platform variability, writing sandboxed extensions, submitting inner-source pull requests, and operating maintainer workflows are maintained in:
- PLE Practitioner Reference: Refer directly to the specialized
product-line-engineering/directory. - Operating Law: The contribution guidelines, version control standards, and code review SLAs detailed in the
product-line-engineering/folder are the non-bypassable architectural rules of the enterprise.