01. Value Domains and Operating Planes

This chapter maps Zeta's work system by detailing how value flows across our strategic domains and operating planes.

1. The Value Domains to Operating Planes Transition

Value moves through Zeta's operating model across four sequential domains, each transitioning into a dedicated operational plane:

VALUE DOMAIN:      [ Pipeline ] ------> [ Platforms ] ------> [ Engagements ] ------> [ Outcomes ]
                                              │                      │                       │
                                              v                      v                       v
OPERATING PLANE:                      Product Platform       Engagement Platforms        The Run
                                           Plane                    Plane                 Plane

To prevent operational silos and ensure absolute clarity on where work is executed, our work system is partitioned into three distinct Operating Planes:

1.1 The Product Platform Plane

• Domain Alignment: Platforms.
• What it represents: The reusable software assets, platform codebases, and core transactional engines (Tachyon, Photon, Electron, Olympus) that represent Zeta's core intellectual property.
• Work Goal: Product maturity, performance scaling, operational efficiency, and standard configuration/variability interfaces.

1.2 The Engagement Platforms Plane

• Domain Alignment: Engagements.
• What it represents: The internal developer and operator platforms that automate, streamline, and make the assembly and delivery of Customer Products repeatable. This plane houses Engagement Readiness Engineering (ERE) for delivery-phase tooling and Engagement Win Engineering (EWE) for operate-phase tooling.
• Work Goal: Compressing the Cost of Activation (COA) and eliminating extraneous delivery friction.

1.3 The Run Plane

• Domain Alignment: Outcomes.
• What it represents: The production operating organization made up of three central Outcomes CoEs (SRE Operations, Processing Operations, and Customer Success) that sustains running, active customer instances in production.
• Work Goal: Achieving high reliability, SLA adherence, security/site assurance compliance, and compressing the Cost of Servicing (CoS).

2. The Engagement Factory: The Connective Spine

The Engagement Factory (EF) serves as the connective structural spine that bridges the three operating planes. It is the organizational engine that assembles raw platform assets from the Product Plane, configures them using tooling from the Engagement Platforms Plane, and transitions the resulting custom Customer Products into the Run Plane for steady-state operations.

The flow of change across these planes is visualized in the following diagram:

graph TD
    subgraph ProductPlane ["Product Platform Plane (Platforms Domain)"]
        coreAssets["Core Assets: Tachyon, Photon, Electron, Olympus"]
    end

    subgraph EngagementPlatformsPlane ["Engagement Platforms Plane (Engagements Domain)"]
        ere["Engagement Readiness Engineering (ERE) - Delivery Tooling"]
        ewe["Engagement Win Engineering (EWE) - Operate Tooling"]
    end

    subgraph RunPlane ["The Run Plane (Outcomes Domain)"]
        sre["SRE Operations CoE (Site Assurance & Runtime)"]
        procOps["Processing Operations CoE (Payment Networks & Compliance)"]
        custSuccess["Customer Success CoE (Support & QRC)"]
    end

    subgraph Spine ["Connective Spine"]
        ef["Engagement Factory (EF)"]
    end

    coreAssets -->|"1. Exposes APIs & Variability Points"| ef
    ere -->|"2. Provides Delivery Toolkits"| ef
    ewe -->|"3. Provides Business Run Tools"| ef
    ef -->|"4. Assembles, Customizes, & Deploys"| RunPlane
    sre -->|"5. Establishes Feedback Loops"| coreAssets

By maintaining this clear operational segregation, Zeta prevents customer-specific delivery pressures from polluting the Product Platform Plane, while ensuring that the Run Plane is supported by standardized, reproducible software assemblies.