Skip to main content
Kuldeep Singh
Kuldeep SinghDigital Architecture
TM FORUM ODA · WEBGPU · REACT FLOW · HYBRID AITier 1 Flagship

TM Forum Open API Intelligence Suite & Spectra AI Copilot

When enterprise JSON payloads become unreadable, transform data contracts into observable, interactive graphs with client-side AI.

Browser-local payload visualization, DAG topology layouts, laser presentation trails, and hybrid WebGPU AI for 23+ TM Forum Open APIs.

TM FORUM ODAWEBGPUREACT FLOWAJVHYBRID AI
LIVE PRODUCTION APP100% In-Browser Execution
Google OAuth Gate · WebGPU Spectra AI
Executive BriefTelco
Domain / ScopeTelco Systems & Applied AI Architecture
Architectural RoleCreator & Principal Systems Architect
Timeline & InitiativeArchitecture & Open Systems Initiative · 2026
Key Verified Invariant

Deployed live to production at tmf.victorkuldeep.com and Cloudflare Workers UAT mirror with global sub-second availability

01 // The Constraint

What Made the Problem Difficult

Modern telecommunications architectures undergoing TM Forum Open Digital Architecture (ODA) transformations rely on over 23 Open APIs (TMF620 Product Catalog, TMF622 Product Ordering, TMF637 Product Inventory, TMF641 Service Ordering, TMF679 Offering Qualification, and related domains). Enterprise payloads in these systems frequently span multi-megabyte, deeply nested JSON documents featuring multi-level product hierarchies, dynamic characteristics, place relationships, and complex pricing elements. Standard text editors and tree viewers become virtually unusable, leading to severe communication friction during architectural reviews and client discovery workshops.

Core Platform Constraint

Systemic Friction

Telco architects, BSS engineers, and solution teams lacked a dedicated visual and analytical medium to inspect, present, and validate complex TMF payloads. Existing generic JSON tools offer no semantic understanding of TM Forum data models, collapse under circular references, offer no schema compliance diagnostics, and lack real-time presentation capabilities. Furthermore, strict enterprise data privacy rules prevent teams from sending sensitive client telecom contracts and quote payloads to third-party cloud AI services for analysis.

Boundary Invariants & Operational Limits:
  • !Must run 100% client-side in the browser with zero mandatory backend server dependencies to protect proprietary enterprise telco data
  • !Sub-second DAG graph rendering and layout for massive hierarchical order and inventory payloads (up to 10MB JSON)
  • !Spectra AI must support local in-browser WebGPU inference (zero token cost, zero data leakage) alongside native direct CORS cloud models
  • !Strict schema validation supporting AJV Draft-07 and 2020-12 across 23+ TM Forum Open API specifications with path-level error diagnostics
  • !Seamless real-time presentation mode with laser pointer drawing trails to facilitate live architectural brainstorming and client discovery
02 // The Architecture

What System Was Designed

Architected as an ultra-fast, client-side Single Page Application (SPA) pairing React Flow (@xyflow/react) with asynchronous graph layout worker threads (Dagre and ELKjs). Built an interactive presentation overlay with mathematical laser trail decay, a real-time schema diffing engine, and an AJV-powered validator. The intelligence layer, Spectra AI Copilot, is engineered as a hybrid AI orchestrator: users can sign in with Google to execute local quantized LLMs (Qwen 3.5 builds) directly on their client GPU via browser WebGPU, or connect directly to cloud reasoning models (DeepSeek, Groq, OpenRouter, OpenAI, and Ollama) with zero backend retention. An IndexedDB vector store enables local RAG over custom user guides with exact specification citations.

03 // The Key Decision

Pivotal Architectural Choices

Key Architectural Decisions

ADR // 01DETERMINISTIC CHOICE

React Flow & Directed Acyclic Graph (DAG) Layouts vs. Static Collapsible JSON Trees

Context:

Nested JSON trees obscure topological relationships between parent/child order items, billing accounts, and qualifying characteristics.

Alternatives Evaluated:
  • Collapsible JSON tree renderers
  • Raw code editors with syntax highlighting
  • Custom SVG canvas from scratch
Chosen: React Flow graph canvas orchestrated with Dagre and ELKjs layout engines inside dedicated Web Workers.

Transforms abstract data contracts into an intuitive visual graph where architects can navigate dependencies, inspect polymorphic attributes, and understand fulfillment topology in real time.

ADR // 02DETERMINISTIC CHOICE

In-Browser WebGPU Local AI + Native CORS Cloud Hub vs. Centralized Heavy AI Server

Context:

Enterprise telco payloads contain commercially sensitive pricing, network topologies, and customer identities that cannot touch third-party servers.

Alternatives Evaluated:
  • Centralized Node.js backend streaming all prompts to OpenAI
  • Requiring every user to install local Python environments
  • Static rule-based validation scripts only
Chosen: Hybrid AI architecture featuring in-browser WebGPU inference via @mlc-ai/web-llm (Qwen 3.5) paired with native browser CORS for cloud models.

Provides 100% data privacy with zero server compute costs. Prompts and weights run purely in local browser memory and WebGPU vRAM.

ADR // 03DETERMINISTIC CHOICE

Real-Time Laser Pointer Presentation Canvas vs. Screen Annotation Plugins

Context:

Architects frequently conduct live virtual sessions to explain complex payload dependencies to stakeholders without screen clutter.

Alternatives Evaluated:
  • Third-party zoom annotation tools
  • Static screenshot markup tools
  • Mouse cursor highlighting
Chosen: Custom SVG pointer drawing surface (LaserOverlay) with fading quadratic bezier trails and 1500ms glow decay.

Allows presenters to naturally guide client attention directly on active nodes without leaving the browser or installing extra software.

ADR // 04DETERMINISTIC CHOICE

AJV Schema Compliance & Live JSON Patching vs. Read-Only Static Validators

Context:

Architects not only need to find errors in payloads; they need to simulate fixes and author schema extensions on the fly.

Alternatives Evaluated:
  • Standard post-call JSON linter
  • Online schema validator sites
  • CLI-only validation scripts
Chosen: Integrated Schema Hub and Schema Builder with path-level JSON patch generation and instantaneous visual feedback.

Accelerates new TMF API development cycles by allowing engineers to modify payloads and verify compliance live.

04 // The Engineering

What Was Actually Built

01

Decoupled layout computation into a dedicated Web Worker (layout.worker.js) utilizing Dagre and ELKjs, keeping the React UI thread at a smooth 60 FPS even when rendering hundreds of node hierarchies.

02

Implemented a dynamic local sliding window memory algorithm for WebGPU inference that automatically scales context to protect browser GPU memory and prevent vRAM exhaustion.

03

Engineered an SVG-based laser trail renderer with decay timers and pointer capture (laserTrail.js), enabling smooth multi-stroke drawing across zoomable canvas surfaces.

04

Constructed a browser-local vector indexing pipeline (docChunker.js, pdfTextExtractor.js, vectorStore.js) using IndexedDB (spectra_chats_db) for local document RAG with API scope tagging.

05

Built dual deployment pipelines: static production on Hostinger CDN (tmf.victorkuldeep.com) and Cloudflare Workers (tmf-visualizer.victorkuldeep.workers.dev) with custom worker routing.

05 // The Trade-offs

Deliberate Architectural Compromises

Trade-offs & Mitigations

In-Browser WebGPU Compute vs Cloud API Model Capabilities

Architectural Benefit:

Zero server hosting cost, zero token billing, and total compliance with strict enterprise data residency rules.

Associated Cost:

Requires client device with WebGPU support (Chrome/Edge/Brave) and initial download of quantized model weights (~500MB - 1.5GB).

Mitigation Strategy:

Engineered a dual-engine Model Hub: users without WebGPU can connect lightweight cloud keys (DeepSeek/Groq) with native CORS or run local Ollama/LM Studio.

Full Client-Side Schema Validation vs Server-Side Verification

Architectural Benefit:

Instant sub-millisecond feedback on every keystroke without network latency.

Associated Cost:

Requires packaging schemas for 23 TM Forum APIs into client bundle chunks.

Mitigation Strategy:

Employed dynamic schema registry caching and lazy-loading for API definitions (TMF620-TMF764).

06 // The Result

Verified Outcomes

✓ VERIFIED RESULT

Deployed live to production at tmf.victorkuldeep.com and Cloudflare Workers UAT mirror with global sub-second availability

✓ VERIFIED RESULT

Comprehensive visual, structural, and compliance support for 23 TM Forum Open APIs spanning Product, Service, Resource, Customer, and Billing

✓ VERIFIED RESULT

Zero server token costs: 100% private in-browser WebGPU AI inference with Qwen 3.5 local models

✓ VERIFIED RESULT

Adopted by architects and BSS engineers for interactive client design sessions using the built-in laser pointer presentation tool

✓ VERIFIED RESULT

Accelerated schema compliance and payload debugging from hours of manual JSON parsing to instant visual diagnosis

07 // Architecture Blueprint

System Schematic & Data Flow

System Topology Blueprint
TM Forum API Visualizer & Spectra AI Copilot Architecture
INTERACTIVE SCHEMATIC
TM FORUM OPEN API PAYLOAD INGRESS (23+ SPECIFICATIONS)TMF620 (Catalog) · TMF622 (Ordering) · TMF637 (Inventory) · TMF641 (Service) · TMF679 (Offering Qual)Multi-Megabyte Polymorphic JSON · Deep Hierarchy Graphs · Place & Party BindingsREACT FLOW DAG CANVAS & LASER OVERLAYAsynchronous Layout Worker (Dagre / ELKjs)• 60 FPS interactive pan, zoom, and node grouping• LaserOverlay: Mathematical decay drawing canvas for client reviews• Live JSON Patch editor with real-time node mutationSCHEMA COMPLIANCE & DIFF ENGINEAJV Worker (Draft-07 & 2020-12)• Path-level error diagnostics & line indicators• Structural schema diffing & regression alerts• Schema Builder for custom ODA extensionsSPECTRA AI COPILOT — HYBRID INTELLIGENCE & VECTOR RAGIN-BROWSER WEBGPU (100% PRIVATE)Qwen 3.5 MLC Quantized Weights (0 Server Cost)Sliding-Window VRAM Management · IndexedDB RAGCLOUD REASONING HUB (DIRECT CORS)DeepSeek · Groq · OpenRouter · OpenAI · OllamaDirect Client-Side Keys · Encrypted Render Proxy

Client-side single-page architecture orchestrating React Flow DAG layout workers, SVG laser drawing canvas, AJV schema compliance, and hybrid WebGPU/Cloud Spectra AI inference.

Text alternative for screen readers: Architecture flow: TMF JSON Payload Ingress to Layout Worker (Dagre / ELKjs) via Background Hierarchy Parsing; Layout Worker to React Flow DAG Canvas via 60 FPS Interactive Graph; React Flow Canvas to Laser Presentation Overlay via Real-Time Decay Trails; AJV Validator Worker to Spectra AI Copilot via Path-Level Diagnostics & WebGPU Fixes

08 // Why It Matters

Architectural Conclusion

TM Forum Open Digital Architecture (ODA) is the global standard for telecom digital transformation. Turning its complex, polymorphic payloads into an observable, interactive visual canvas with private client-side AI empowers architects to design, explain, and validate systems with unprecedented speed.

Key Lessons for Platform Scale:
  • Data contracts should not be locked in raw text; visual topology reveals structural defects that syntax highlighting cannot.
  • Client-side WebGPU and browser-local RAG represent the future of enterprise AI for confidential customer payloads.
  • Building specialized, domain-tailored visual tools elevates architectural influence far beyond standard slide decks and static documentation.