NMQ Investor Document

MASTER CORE

================================================================================
                       NO MORE QUIET TECH HOLDING
         [ PREMIUM DARK CYBERPUNK B2B TECHNICAL SPECIFICATIONS ]
================================================================================
FOUNDER / CHIEF ARCHITECT: Dejan Milosevic
OFFICIAL CONTRACT EMAIL: dejanswat@gmail.com
CORE INFRASTRUCTURE: W:\ Drive Local PostgreSQL (Port 5433) & Docker
================================================================================

--------------------------------------------------------------------------------
DOCUMENT 2: iGaming_Master_Core_v4.0_Internal_Lab.txt
--------------------------------------------------------------------------------
[ STAGE: IMMUTABLE GOLDEN MASTER ]
[ THEME: DEEP CHARCOAL / LIGHT ICE BLUE ACCENTS ]

1. THE "GOLDEN MASTER" CONCEPT

The iGaming Master Core v4.0 functions exclusively as an immutable reference
blueprint and clean development engineering laboratory on your local machine.
Its purpose is to remain in a pristine, un-altered state, serving as the master
template from which advanced commercial branches (such as the NMQ Enterprise
branch) are derived.

Development Rule: Source files inside the 'premium-casino' and 'affiliate-tracker'
directories running on ports 3000 and 4100 are never changed during white-label
customizations. They serve to verify base math, core loops, and webhook telemetry.

2. LOCAL CONVERSION & WEBHOOK PIPELINE

The master core maps out a clean, linear 3-step tracking architecture across
ports 3000 and 4100 on your local machine:

  - Step 1 - Click Ingestion: The user generates traffic via an affiliate link.
    The Tracker (4100) handles the request, instantiates a unique token string
    ('aff_click_uid'), sets it inside a browser cookie context, and triggers a
    302 redirect to the Casino (3000).

  - Step 2 - Registration Hook: When an account is registered on the casino, the
    backend reads the matching browser cookie and fires an asynchronous
    'REGISTRATION' webhook back to the tracker.

  - Step 3 - Financial Ledger Events: During real-time gameplay across Slot,
    Crash, or Plinko, the casino backend pushes asynchronous POST payloads
    containing encrypted 'DEPOSIT' and 'LOSS' logs to:

    => POST http://127.0.0.1:4100/api/v1/webhooks/casino-event

All authentication loops between the systems are checked via custom request header
states and a shared 'CASINO_SECRET_KEY'.

LAB REPOSITORY SUPPORT: dejanswat@gmail.com

================================================================================
END OF DOCUMENT 2 — iGaming Master Core v4.0 Internal Lab
================================================================================