What this register does.
Programming Logic Specification v4 resolved several earlier ambiguities, but a number of rules remain either mis-stated or undefined. This document lists each one, classifies who owns the decision, and proposes wording for approval.
Rules that can be fixed from the existing model, worked examples and acceptance tests — no new commercial decision needed.
Rules the source material cannot determine. Genaris, Finance or Compliance must approve the intended treatment before build.
Each open item carries draft wording. Placeholders in brackets are the values that must be supplied at approval.
- Maximum Qualifying Builder Volume = Influencer Volume × 1.5
- Qualifying Builder Volume = min(Builder Volume, Influencer Volume × 1.5)
- Non-Qualifying Builder Volume = max(0, Builder Volume − Qualifying Builder Volume)
- Balance Ratio (where Influencer Volume > 0) = Builder Volume ÷ (Influencer Volume × 1.5)
- Maximum Total Qualifying Volume = Influencer Volume × 2.5
How each item is classified.
Every register item carries exactly one classification. The classification determines who must approve it before programming may proceed.
The issue identified in the original review has been adequately addressed in Programming Logic Specification v4.
The intended rule can be established from the existing model, worked examples and/or acceptance tests. The specification should be corrected without requiring a new commercial decision.
The source material does not contain sufficient information to determine the commercial rule. Genaris must approve the intended treatment.
The rule principally concerns revenue recognition, accounting, currency, deductions, reversals, rounding or settlement.
The rule raises legal, regulatory or compensation-plan compliance considerations and should not be activated without explicit approval.
Consolidated decision register.
Filter by owner or search by keyword. Blocking items must be resolved before the corresponding logic is programmed.
| ID | Issue | Classification | Priority | Blocks programming? |
|---|---|---|---|---|
| GDR-01 | Balance Ratio uses 2.5 instead of 1.5 | Specification Correction | Critical | Yes |
| GDR-02 | 2.5 terminology confused with total qualifying volume | Specification Correction | Critical | Yes |
| GDR-03 | Group 1 / Group 2 terminology | Resolved | — | No |
| GDR-04 | Builder Influencer-Team tiers are flat/cliff tiers | Genaris Decision Required | High | Yes – commercial sign-off |
| GDR-05 | Influencer personal commission tier treatment | Resolved | Medium | No |
| GDR-06 | Productive Builder Team branch/depth definition | Resolved | Medium | No |
| GDR-07 | Builder-side commissionable genealogy depth | Genaris Decision Required | Critical | Yes |
| GDR-08 | Minimum volume required for a Productive Builder Team | Genaris Decision Required | Critical | Yes |
| GDR-09 | Inactive-member / termination compression | Genaris Decision Required | Critical | Yes |
| GDR-10 | Net Sales Revenue definition | Finance Decision | Critical | Yes |
| GDR-11 | Commission-period definition and timezone | Finance Decision | High | Yes |
| GDR-12 | Order-recognition event | Finance Decision | Critical | Yes |
| GDR-13 | Refund and return treatment | Finance Decision | Critical | Yes |
| GDR-14 | Chargebacks and commission clawbacks | Finance Decision | Critical | Yes |
| GDR-15 | Negative volume / negative commission treatment | Finance Decision | High | Yes |
| GDR-16 | First two whole months / partial enrolment | Genaris Decision Required | High | Yes |
| GDR-17 | Role changes during commission period | Genaris Decision Required | High | Yes |
| GDR-18 | Sponsor / placement changes | Genaris Decision Required | High | Yes |
| GDR-19 | Termination / suspension | Genaris Decision Required | High | Yes |
| GDR-20 | Customer attribution | Genaris Decision Required | High | Yes |
| GDR-21 | Influencer attribution | Genaris Decision Required | High | Yes |
| GDR-22 | Excess Influencer Volume carryover | Genaris Decision Required | Medium | Yes |
| GDR-23 | Non-qualifying Builder Volume carryover | Genaris Decision Required | Medium | Yes |
| GDR-24 | Retail Margin / purchase credit | Genaris Decision Required | High | Yes if launched |
| GDR-25 | Signup packs | Compliance Decision | High | Yes if launched |
| GDR-26 | Recruitment reward | Compliance Decision | Critical | Yes if feature retained |
| GDR-27 | Currency and FX conversion | Finance Decision | High | Yes for multi-currency launch |
| GDR-28 | Calculation and payout rounding | Finance Decision | High | Yes |
| GDR-29 | Payout timing / reserve period | Finance Decision | Medium | Yes |
| GDR-30 | Minimum payout threshold | Finance Decision | Medium | Yes |
| GDR-31 | Commission caps | Compliance Decision | Medium | Market dependent |
| GDR-32 | Effective-dated plan parameters | Resolved | — | No |
| GDR-33 | Audit / reproducibility requirements | Resolved | — | No |
| GDR-34 | Plan amendment governance | Genaris Decision Required | High | Yes |
| GDR-35 | Balance Ratio zero-volume treatment | Specification Correction | High | Yes |
| GDR-36 | Acceptance-test alignment after corrections | Specification Correction | Critical | Yes |
Every item, in full.
Expand an item to read the finding, the decision required, and the proposed approved wording. Bracketed placeholders are the values Genaris, Finance or Compliance must supply.
Immediate specification corrections.
These corrections require no new commercial decision and should be applied to the Programming Logic Specification now.
- 01GDR-01 — Balance Ratio denominator: 2.5 → 1.5
- 02GDR-02 — Define 2.5 only as the Total Qualifying Volume multiplier
- 03GDR-35 — Formalize the zero-safe balance calculation
- 04GDR-36 — Reconcile acceptance tests and terminology with the corrected formula
Who needs to decide what.
Programming of the affected logic cannot begin until each of these has an approved rule recorded in the Programming Logic Specification.
- GDR-04 Confirm declining flat Builder tiers
- GDR-07 Builder genealogy depth
- GDR-08 Productive-team minimum
- GDR-09 Compression
- GDR-16 Grace-period timing
- GDR-17 Role changes
- GDR-18 Sponsor/placement changes
- GDR-19 Termination/suspension
- GDR-20 Customer attribution
- GDR-21 Influencer attribution
- GDR-22 Excess Influencer Volume carryover
- GDR-23 Non-qualifying Builder Volume carryover
- GDR-24 Purchase credit
- GDR-34 Plan amendment governance
The gate before programming.
No requirement in the Balanced Growth Model is considered approved for production until all five conditions below are satisfied. Developers must not resolve open rules by interpretation.
- 01The business rule has been formally approved by the responsible owner.
- 02The approved rule has been written into the Programming Logic Specification.
- 03Positive, negative and boundary acceptance tests exist for that rule.
- 04Each test states a deterministic expected result, not “Business Rule Required”.
- 05The tests have been signed off by the business owner and by QA/Finance as applicable.
Balance Ratio tests shall specifically use the approved 1.5 Builder-support multiplier.
Acceptance of the decision register.
Signature confirms the specification corrections listed above and acknowledges the outstanding Genaris, Finance and Compliance decisions that must be approved before the affected logic is programmed. A confirmation email is sent to each signer and copied to max@luup.com.
- PLSProgramming Logic Specification v4
- BGMBalanced Growth Model — compensation source document
- ATMAcceptance test matrix (BG series)
- GDRGap & Decision Register — this document