Skip to main content

Integration lanes

Lanes describe how tightly a product is wired into DIC. Pick the lane that matches your product — do not invent a fourth model.

Lane A — standard capability​

Most suite products. You ship:

  • a capability descriptor (how DIC finds your upsert URL, origin path, health),
  • a thin upsert (PUT Collection metadata from the Control Plane),
  • an origin route when the user creates the project inside your UI first.

Descriptor-first means: extend the shared product-capability table / SDK descriptor before you hard-code product id switches in routes.

Typical examples: analytics, audit, brand, creation-style capabilities that mirror the same Collection everywhere.

Lane B — Collection-scoped companion​

A companion that always lives inside an existing Collection. Often externalProjectId === platformProjectId. You still respect Access Model B, but you may not own a full origin create flow.

Think: helper surfaces that never appear as a stand-alone “home” project.

Lane C — workspace product​

Own workspace semantics. Federation is product-specific; you are not auto-listed with Lane A mirrors. Document your contract carefully and keep Collection ids explicit when you hand off into Lane A products.

Upsert vs origin (Lane A)​

DirectionNameWho starts
Control Plane → your productUpsertCollection created/updated in DIC; you mirror
Your product → Control PlaneOriginUser clicked “create” in your UI; DIC creates/binds and syncs siblings

Both directions must stay idempotent. Retries happen.

Upsert: DIC --PUT--> your /api/.../projects/{platformProjectId}
Origin: your UI --POST--> DIC /api/platform/provisioning/{product}-project-origin

Choosing quickly​

QuestionLane
Should creating a Collection in DIC automatically provision me?A (upsert)
Do users sometimes create first inside my product?A (origin + upsert)
Am I only meaningful inside an already chosen Collection?B
Do I have a completely different workspace model?C (talk to the DIC team early)

What usually goes wrong​

MistakeFix
Copy-pasting origin handler bodies per productUse the shared Lane A origin helper from the SDK / scaffold
Skipping the descriptor and switching on product ids in five placesExtend the descriptor once
Non-idempotent upsertUpsert must upsert — second call with same id is success, not conflict chaos

Next: Collections and access · Existing backend · Onboarding recipe