Skip to main content
LuminaryWorks启明工坊

01 / ECOSYSTEM

Ecosystem & architecture

Six products run independently and compose as a federated suite through open protocols and an optional shared control plane — what is shared is identity, entitlement and protocols, never business logic.

01 / VALUE CHAIN

Value-chain loop

Creation and learning lead to device connectivity and data insight, then visual security and remote operations, and finally settlement where agents and humans are peers.

  1. 01

    BlockyEdu智码工坊

    Create

    Skills, artifacts and training content

  2. 02

    SyncroBrain万物智脑

    Connect

    Device onboarding, telemetry, incidents and Safety Kernel

  3. 03

    DataLuminary数据明鉴

    See

    Reports, dashboards, exports and embeds

  4. 04

    VistaCast视界云遥

    Watch

    Visual events, alert state and acknowledgements

  5. 05

    VistaRemote视界远程

    Control

    Remote sessions, recording and audit

  6. 06

    DoerFlow智工网

    Earn

    Tasks, receipts and ledger settlement

02 / PLATFORM

Shared platform

The control plane is optional; product planes stay autonomous. When central services stop, each product degrades exactly as its manifest declares — Casbin is never bypassed.

CONTROL PLANE

Identity (OIDC)

One OIDC login surface for six brands; each product keeps its own logo and copy.

LogtoOIDCPKCE

Central Entitlement

Plans, Trial, License, seats and billing in one place; commercial rights never enter the JWT.

NestJSPostgreSQL

Resource ACL (PAL)

Resource-level ACL stays in each product; permissions ship with the resource.

CasbinPAL

CAPABILITY UNITS

AI gatewaylab

Multi-vendor model routing, key vault and usage metering.

labBYOK

Notification

Shared mail and notification module with a unified sender identity.

@luminaryworks/notification

Shared packages

Identity, ACL and entitlement clients ship as npm packages — no cross-repo source imports.

@luminaryworks/*

03 / INTEGRATION

Integration matrix

Cross-product integration uses OIDC, HTTP, MQTT and versioned events only — no runtime imports or shared business schemas.

Allowed

  • OIDC identity federation
  • HTTP REST export / embed
  • MQTT / CloudEvents
  • Explicit binding records (no implicit joins)

Forbidden

  • Cross-product runtime imports (file: paths, direct source references)
  • Shared business schemas / shared business databases
  • Reusing another product's JWT for resource authorization
  • Embedding commercial rights in JWTs

04 / ERRORS

Unified error semantics

HTTP status codes mean the same thing across products for orchestration and audit.

  • 401Identity

    AuthN failed; identity outages never degrade to anonymous access.

  • 402Entitlement

    Commercial rights insufficient (Trial expired, plan mismatch, quota exhausted).

  • 403Resource ACL

    Casbin denial; License never bypasses resource permissions.

05 / PROTOCOLS

Open-protocol inventory

Integrate through open standards first to reduce lock-in and migration cost.

OIDCMQTTRESTWebRTCONVIF

06 / AUTONOMY

Product autonomy (hard constraint)

Each product owns its database, migrations, Casbin policy and release cadence. It must still start and pass readiness when every sibling product is down.

  • Each product owns its database, migrations, Casbin policy and release cadence
  • It must still start and pass readiness when every sibling product is down