Jira progress: loading…

W-LAB

White Labelling

1. Strategic Positioning: ZAYAZ as the ESG Engine

Core Idea ZAYAZ is the computational fabric of ESG — the engine that measures, validates, and generates sustainability intelligence for any organization, framework, or system.

• ZAYAZ = the data engine, formula brain, and interoperability layer.
• EcoWorld =the curated branded experience with engagement, guidance, and education. EcoWorld Academy, e-c-o.com blog, E-C-O^™ Number and Score lookup,
• White-label partners = “OEM reskinners” — consulting, assurance, or tech partners that deliver the ZAYAZ core inside their client ecosystems, with their own UI/UX, but the same ZAYAZ intelligence beneath.

The key message is that ZAYAZ is the universal computation and compliance logic — the hidden but trusted core everyone builds on.

1.1. Layered Brand & Platform Hierarchy

Layer	Role	Example Entities	Brand Identity on Output	Revenue / Licensing Model
Tier 1 — ZAYAZ Core	Engine for data logic, computation, and verification	DaVE, VTE, FOGE, RIF, NETZERO, COSE, etc.	Invisible or embedded signature (“Computed by ZAYAZ™”)	Engine licensing, per-API transaction
Tier 2 — White-Label Partners	Consulting, accounting, and verifier firms reskinning ZAYAZ	PwC ESG+, DNV-Sustain, ERM GreenLedger	“XYZ ESG Suite — Powered by ZAYAZ™”	White-label licensing + verifier transaction revenue
Tier 3 — Embedded / Developer Integrations (future)	Developers embedding one or more modules	IoT providers, ERPs, analytics vendors	Their brand, “ZAYAZ Verified Integration” tag	API revenue per call / seat

This keeps ZAYAZ authoritative but discreet, visible only as a trust mark or verification engine, never competing with partners.

1.2. Brand Architecture & Signature Logic

This is expressed through a unified Brand Signature Framework rather than a tagline.

Each brand level carries its own signature:

Context	Brand Signature	Purpose
Platform dashboards, APIs	“Runs on the ZAYAZ ESG Engine™”	Signals reliability of the underlying logic
Reports, outputs, or assurance files	“Verified through ZAYAZ Trust Fabric™”	Indicates integrity and audit traceability
White-label partner portals	“Powered by ZAYAZ Intelligence™”	Partner-neutral, reassuring end-users
Developer integrations	“ZAYAZ Verified Module™”	Certifies third-party module compliance

1.3. Experience Model

The product needs both universality and embeddedness.

Key architectural enablers:

Pillar	ZAYAZ Capability	Outcome
Universal Data Model	USO / SSSR → unified signal registry and ontology	Any ESG dataset becomes ZAYAZ-readable
Formula Engine	Computation Hub (NETZERO, FIRM, COSE)	Complex logic computed instantly, like Excel formulas
Interoperability Layer	DSAIL + APIs + NACE/IPCC mappings	Connects to IoT, ERP, accounting, and verification systems
Trust Layer	DaVE + VTE + ALTD blockchain audit	Every calculation has provenance
Interface Flexibility	SEEL + SDK / white-label skins	Partners can re-brand without altering logic
Scalability	Containerized micro-engine structure (MICE)	Modular deployments, on-prem or cloud

1.4. Implementation Blueprint for White-Labelling

Phase	Action	Technical / Brand Deliverable
1	Define ZAYAZ White-Label SDK	Secure containerized bundle of SEEL + Input Hub UI modules
2	Build Partner Console	Admin interface for managing partner branding, clients, and E-C-O numbers
3	Establish Signature Injection Framework	Automated embedding of “Verified through ZAYAZ” metadata in all reports
4	Create ZAYAZ Trust Registry	Public lookup showing which partner systems are validated on ZAYAZ
5	Develop Co-Brand Templates	White-label UI themes, report header/footers, and API branding fields

1.5. Governance & Commercial Rules

• Data Sovereignty: All partner data processed through ZAYAZ core must retain blockchain hash for traceability.
• Partner Autonomy: Partners control UI/UX but not computation logic — ensures consistency in ESG results.
• Transparency Layer: Every white-label report embeds a ZAYAZ Verification Header (machine-readable JSON) for authenticity.
• Revenue Model:
  • Engine license (core access)
  • Transactional fee per verified report
  • 3 tier annual subscription model. Split handled by Stripe or customised.
  • Premium AI features (ZARA, FIRM) as modular add-ons

1.6. Visual Identity Strategy

A minimalist symbol for the core — not flashy, but technical and precise.

Think: a geometric “Z Core Mark” or circular verification seal that partners can overlay unobtrusively.

Each seal could correspond to a Trust Level:

Seal Tier	Meaning
Z-Base	Using ZAYAZ computational engines
Z-Verified	Includes blockchain traceability and verification workflow
Z-Autonomous	Fully autonomous ESG computation, no human intervention

1.7. Future Scalability

This layered model easily expands to:

• API marketplaces for module-level integrations
• Developer ecosystems where others can extend ZAYAZ modules
• Embedded verification in IoT and ERP systems via Z-Edge + MAS

In short, we’ll become the ESG OS — the Operating System for Sustainability Data.

2. ZAYAZ White-Label Governance & Partner Framework

A foundational specification for brand licensing, technical integration, and trust assurance

2.1. Purpose & Strategic Principles

Objective Define rules, standards, technical requirements, and trust protocols that enable partners to white-label ZAYAZ while ensuring:

• Identical computational outcomes
• Data integrity
• Brand protection
• Transparent trust signalling
• Seamless integration with the ZAYAZ ecosystem

Core Principles

1. ZAYAZ is the ESG computation and verification engine.

• Partners may customize experience, but never alter logic, calculations, or validation processes.

2. White-labelling enhances reach without diluting integrity.

• ZAYAZ’s presence is subtle and authoritative—visible as a verification layer, not a consumer-facing brand.

3. Partners control UX; ZAYAZ controls truth.

4. Every output must carry a ZAYAZ Trust Signature.

• (machine-readable for audit, optional visual seal for clients)

5. Developer extensibility is future-proofed.

• Module-level APIs will allow external developers to embed ZAYAZ engines into third-party ESG tools.

2.2. Partner Types & Permission Levels

Partner Type	Branding Rights	Feature Rights	Trust Level	Examples
White-Label SaaS Partners (WL-1)	Full re-skin	Full access to ZAYAZ platform modules	Z-Base or Z-Verified	Big-4 ESG divisions, regional ESG platforms
Verification & Assurance Partners (WL-2)	Co-brand only	Verification workflows + DaVE/VTE	Z-Verified	Auditors, certification bodies
Implementation & IoT Partners (WL-3)	“Integration Partner” mark	API access + telemetry ingestions	Z-Base	Nordic Semiconductor, ERP/IoT vendors
Developer Ecosystem (WL-4, future)	No branding rights	Module-level API licensing	Z-Base	Independent devs embedding specific modules

Each partner type receives a Partner Passport describing their rights, branding assets, and technical allowances.

2.3. Brand Governance: Signatures, Seals & Usage Rules

ZAYAZ must appear consistently across all outputs—but subtly.

Mandatory ZAYAZ Trust Signature on All Outputs

Every report, API response, dashboard export, or data packet must embed: ZAYAZ Verification Header (ZVH)

A machine-readable JSON block containing:

• Engine version (FOGE, DaVE, VTE, NETZERO, RIF)
• Calculation hash
• Verification status
• Data provenance flags
• Timestamp
• PartnerID

Example:

verification-header.json

{
  "computed_by": "ZAYAZ Engine v7.4",
  "trust_level": "Z-Verified",
  "verification_hash": "0x821ab3…",
  "partner_id": "WLP-2025-183",
  "daVe_score": 92,
  "vte_provenance": "autonomous",
  "timestamp": "2025-11-15T09:12:44Z"
}

This guarantees the integrity of ZAYAZ logic even under a full white-label façade.

Optional Visual Signatures (Partner controls placement)

Choose from three Trust Seals:

Seal	Meaning	Usage
Z-Base™	Calculations performed using ZAYAZ engine	All WL partners, default
Z-Verified™	Includes DaVE+VTE checks + blockchain audit	Assurance partners, regulated markets
Z-Autonomous™	Fully autonomous ESG computation, no human override	High-trust outputs

Partners may place these seals:

• On report footers
• In dashboard “Data Integrity” modal
• In APIs as metadata tags

But NOT:

• As the main brand
• In UI headers
• In login screens

The seal must always remain secondary to the partner’s brand.

2.4. UI/UX Governance

What Partners May Change

• Logos
• Colors
• Typography
• Navigation layout
• Landing pages
• Content text
• Localized field names
• Report templates (design only)

What Partners May Not Change

• Core logic (calculations, validation rules)
• Input modules and their underlying structure
• SEEL materiality logic
• FOGE field behavior
• DaVE/VTE scoring logic
• Carbon Passport computation
• E-C-O Number rules
• API structure
• Blockchain audit requirements

This ensures all white-label products are technically identical to ZAYAZ.

2.5. Technical Architecture Rules

Partners receive the ZAYAZ White-Label SDK which includes:

Core Components

• SEEL + Input Hub (UI modules)
• FOGE form generator engine
• DaVE validator + VTE trust engine
• Computation Hub (RIF, NETZERO, FIRM)
• API gateway for partner routing
• Branding injection module
• Telemetry ingestion router (for IoT/Matter partners)
• Verification event logger
• Blockchain sync client (ALTD)

Deployment Models

• Cloud multi-tenant (default)
• Cloud single-tenant (enterprise)
• Hybrid with local Z-Edge nodes
• On-prem enterprise (rare) — Only with ZAYAZ technical oversight

Data Flow Rules

• All calculations MUST run through ZAYAZ engines
• All trust events MUST be logged to ZVS (ZAYAZ Verification Store)
• All sensitive logic MUST be validated via signature check

2.6. Partner Compliance Requirements

Each partner must pass:

Brand Compliance Certification

• Correct ZAYAZ seal usage
• Correct placement of ZAYAZ metadata
• Fully compliant white-label UI theme

Technical Compliance Certification

• Daily trust event logging
• Verification header integrity
• Valid DaVE/VTE integration
• No attempted override of logic
• Proven accurate E-C-O Number routing

Governance Review

Annual review:

• Data integrity audit
• Security controls
• Algorithm integrity
• System usage compliance

2.7. API & Module Licensing Rules

White-Label Partners (WL-1)

• Full API suite
• Unlimited branded UI instances
• Tiered pricing based on client volume
• Access to module add-ons (FIRM, PEF-ME, NETZERO Forecasting)

Developer Ecosystem (WL-4, future)

Pricing per:

• API call
• Data volume
• Engine transaction
• Validation event
• Like AWS Lambda but for ESG intelligence.

2.8. Commercial Rules

Revenue Streams (depending on agreement)

• White-label license fees
• SaaS annual revenues sharing - Stripe or customised. solutions
• Usage-based computation fees
• DaVE/VTE verification fees
• Carbon Passport fees
• E-C-O Number issuance
• Setup fees
• API call revenue
• IoT telemetry routing

Partner Incentives

• Bulk discounts
• Co-marketing
• Preferred partner ranking (e.g., Platinum Integration Partner)
• Access to advanced modules early

2.9. Future Extensions

• Developer Marketplace for ZAYAZ micro-engines
• Global ZAYAZ Trusted Integration Registry
• Machine-readable partner scorecard
• AI co-pilot for partner developer tools
• Federation model for national ESG hubs
• “ZAYAZ Embedded” program for Matter/IoT vendors

3. ZAYAZ White-Label SDK Architecture Overview

3.1. Purpose

The ZAYAZ White-Label SDK lets partners:

• Embed ZAYAZ as their ESG engine while using their own branding.
• Use a consistent API surface for forms, metrics, validation, trust, and reporting.
• Integrate with IoT / telemetry, verification workflows, and the Computation Hub.
• Guarantee that all outputs are “ZAYAZ-true”.

SDK = a set of frontend, backend, and infra components:

• Frontend Web SDK (React/Vue components, theming hooks)
• Backend API Client SDKs (TypeScript/Node, Python; others later)
• Infrastructure & DevOps artifacts (OpenAPI spec, Postman collection, webhook patterns)

3.2. High-Level Architecture

Think of the SDK as three concentric layers:

1. Core Engine Layer (inside ZAYAZ, not exposed as code)

• FOGE, SEEL, DaVE, VTE, Computation Hub (NETZERO, FIRM, etc.)
• Runs entirely in ZAYAZ-controlled environments.

2. Integration / API Layer

• REST/GraphQL APIs and Webhooks.
• Tenant isolation, auth, rate limiting, versioning.

3. SDK & UI Layer

• White-label UI components.
• API clients & helpers.
• Branding & config.

[ Partner UI / Apps ]
    ▲   ▲
    |   |
[ SDK & UI Layer ]  --> React/Vue components, TS/Python SDK
        ▲
        |
[ Integration Layer ] --> REST/GraphQL, Webhooks, OAuth2/JWT
        ▲
        |
[ Core Engine Layer ] --> FOGE, DaVE, VTE, NETZERO, FIRM, PEF-ME, etc.

3.3. Modules in the SDK

1. Core Client Libraries

• zayaz-core-js (TypeScript/Node)
• zayaz-core-py (Python)
• Later: zayaz-core-php, zayaz-core-dotnet if needed

Features:

• HTTP client with built-in retry & backoff.
• Auth handling (API keys, OAuth2 client credentials, or JWT).
• Strong models for:
• Tenants / Clients
• Forms / Form Templates
• Submissions
• Validation Results
• Metrics / KPIs / ESRS datapoints
• Trust Objects (DaVE/VTE outputs)
• Carbon Passport / E-C-O Number lookups.

2. Frontend / UI SDK

• zayaz-ui-react (first-class)
• Later optional: zayaz-ui-vue

Components:

• Form Components

  • <ZayazForm /> – renders FOGE-driven form by form_id.
  • <ZayazField /> – field-level component, supports FOGE metadata (required, unit, AI hint, etc.).
  • <ZayazSection />, <ZayazGroup /> – chunking forms into modules (Waste, Energy, etc.).

• Trust & Verification Widgets

  • <ZayazTrustBadge trustLevel="Z-Verified" />
  • <ZayazDataIntegrityPanel submissionId="..." />

• Metrics & Dashboard Widgets

  • <ZayazMetricCard metricCode="E1-1" />
  • <ZayazKpiTable naceCode="..." />

• Theming / Branding

  • Config object:

ui-provider.ts

ZayazUIProvider theme={{
  primaryColor: "#partner",
  logoUrl: "/partner-logo.svg",
  fontFamily: "partner-font",
  showZayazBranding: false, // white-label mode
  showZayazTrustSeal: "minimal", // none | minimal | full
}}>

3. Configuration & Tenant Module

• Tenant bootstrap & mapping:

  • tenant_id = partner sub-instance.
  • client_id = end-customer within partner.

• Controls:

  • Enabled modules (e.g. FIRM, NETZERO, Carbon Passport).
  • Regional rules (ESRS / EU taxonomy toggles, local rules).
  • Trust thresholds (minimum DaVE score, VTE level required).

4. Validation & Trust Integration The SDK wraps DaVE / VTE endpoints:

• validateSubmission(submissionId) → validation score + issues.
• getTrustSummary(submissionId) → DaVE score, provenance flags, etc.
• Helper to embed ZAYAZ Verification Header into partner outputs.

5. Telemetry / IoT & Z-Edge Integration (for partners like Nordic)

• Optional zayaz-iot-client:

• Register device → obtain device token.

• Submit telemetry events (energy, flow, sensor metrics).

• Link device to:

  • Facility
  • E-C-O Number
  • Product / CPI

6. Webhook & Event Subscriptions

• SDK helpers to register & manage:
  • on_form_submitted
  • on_validation_completed
  • on_metrics_updated
  • on_trust_score_changed
  • on_cpi_verified

3.4. Packaging & Distribution

• OpenAPI spec → auto-generate clients, Postman, etc.
• NPM packages for JS/TS.
• PyPI package for Python.
• Example repos:
  • zayaz-sdk-examples-js
  • zayaz-sdk-examples-react
  • zayaz-sdk-examples-python

3.5. Security & Multi-Tenancy

• JWT / OAuth2 for partner apps.
• Per-tenant rate limits and quotas.
• Enforced mapping: each request goes through:
• partner_id
• tenant_id
• client_id
• Audit log for:
• Access to trust results
• Engine versions used
• Changes to thresholds/config

4. Developer API Documentation Outline

This is the table of contents + structure for the API docs — available at the Docusaurus doc portal/site.

1. Intro Section

2. Getting Started

3. Core Resources & Endpoints

4. Events & Webhooks

5. ZAYAZ Trust & Verification Header (ZVH)

6. SDK Usage Examples

7. Security, Compliance & Logging

8. Advanced Topics (Later Docs)

9. Changelog & Deprecation Policy

5. The Two Types of White-Label Partners