Public documentation

Product architecture

An overview of the systems that power the Lumen Consulting client platform — from the presentation layer through the intelligence tier down to storage and observability.

Layered view

Each tier is deployed independently, versioned independently, and observable end-to-end.

Presentation

Client-side

React + TypeScript SPA served over a global edge network. Role-scoped workspaces, live progress, and full offline resilience for read paths.

React 19

TanStack Router

Tailwind v4

Radix Primitives

Interaction & Orchestration

Edge

Edge functions handle authentication, request validation, and orchestration between service tiers. Sub-100ms fanout to internal services.

TanStack Start

Cloudflare Workers

Zod validation

Intelligence

AI Tier

Structured extraction of business problems, automatic tagging, and consultant-match scoring. All prompts human-reviewed before rollout.

LLM Gateway

Vector search

Retrieval pipelines

Guardrails

Domain services

Core

Requests, engagements, calendars, billing, and CRM — each a bounded context with its own data ownership and public contract.

Requests

Scheduling

Notes

People

Analytics

Data

Storage

PostgreSQL for transactional state, object storage for artifacts, and a governed data warehouse for analytics workloads.

PostgreSQL

S3-compatible object store

OLAP warehouse

Platform

Ops

Observability, identity, secrets, and deployment. Every change is version-controlled, reviewed, and rolled out with automated gates.

OpenTelemetry

OIDC

Secret manager

Automated rollouts

Request lifecycle

A client-submitted engagement flows through the following stages, each with a clear owner and SLA.

Step 1

SLA · instant

Submission

Client submits an engagement with budget, timeline, and problem statement.

Owner

Client

Step 2

SLA · < 2s

Auto-summary

The system extracts a summary, tags, and complexity signals from the free-form input.

Owner

Intelligence tier

Step 3

SLA · < 5 min

Routing

A duty partner reviews and assigns the request to a matching consultant team.

Owner

Duty partner

Step 4

SLA · < 4 h median

First contact

Consultant reaches out to align on scope and book a discovery meeting.

Owner

Assigned consultant

Step 5

SLA · typically day 3–7

Kickoff

Kickoff meeting confirms the plan, roles, and deliverables cadence.

Owner

Engagement lead

Step 6

SLA · per plan

Delivery & closeout

Weekly cadence, milestone-based deliverables, and a formal handover at closeout.

Owner

Engagement lead

Cross-cutting concerns

Non-functional requirements applied at every tier.

Security & privacy

SOC 2-aligned controls, encryption at rest and in transit, per-tenant data isolation, and least-privilege access reviewed quarterly.

Reliability

Multi-region active/passive for critical paths, automated failover drills, and a documented incident-response runbook.

Observability

Distributed traces, structured logs, and SLO-driven alerting across every domain service.

Access control

Role-scoped workspaces (Client, Consultant, Administrator), enforced at the edge and again in every domain service.