Welcome to DIC
Digital Impact Connection (DIC) is the shared layer between your product app and the rest of the suite: identity, Collections, access, and the contracts that keep every product talking the same language.
You are in the right place if you want to:
- spin up a new product that plugs into DIC,
- connect an existing backend to Collections and login,
- or look up a TypeScript helper, REST path, or GraphQL query without hunting through the monorepo.
The mental model (30 seconds)
| Piece | What it is | What you use |
|---|---|---|
| DIC Control Plane | Identity, Collections, members, provisioning | Staging host such as https://plexon-v3.projects-a.plygrnd.tech |
| DIC SDK | Shared wire types, headers, OpenAPI, GraphQL SDL | @chbrdk/plexon-federation |
| App Framework | UI shell, jobs, banners, uploads — no secrets inside | @chbrdk/dic-app |
| Your product | Domain logic and screens | Your Next.js (or other) app |
A Collection is the only project the user sees. CHECKION, AUDION, METRON, and the others are capabilities hanging off that Collection — not separate “projects” you invent in the UI.
Where to go next
- New product? → Lane A Quickstart
- Existing API? → Connect an existing backend
- Need the why? → Collections and access · Lanes · Auth
- Building UI? → App Framework
- Looking up a symbol? → TypeScript · REST · GraphQL
Versions this docs build cares about
| Artefact | Pin |
|---|---|
| Federation wire | 2026-05-plexon-federation-v3 |
| SDK package | @chbrdk/plexon-federation@0.2.1 |
| App package | @chbrdk/dic-app@0.1.0 |
| Docs generator | Docusaurus 3.10.2 |
Downloads for this build: OpenAPI · GraphQL SDL · manifest.
Language
Guides ship in English and German. API names, package imports, and HTTP paths stay English everywhere — that is intentional so snippets stay copy-pasteable.