Stitched connections
Compose several databases into one conversation so a question can span all of them.
A stitched config joins two to five connections into a single queryable surface. The chat then reads them as one database, useful when your billing data and your product data live apart.
Create one
Select the connections to compose. ChatPlotDB inspects each schema and proposes the join keys that link them.
The refinement gate
A stitched config is not usable the moment it is created. It starts in a "needs refinement" state until the join keys are verified, because a wrong join across databases produces answers that look plausible and are silently wrong: rows multiplied by a bad cardinality, or dropped by an inner join.
Verify each proposed key, then save.
Lazy schema loading
Child schemas load per database rather than all at once, so composing five large databases does not mean waiting for five full introspections before you can ask anything.
When not to stitch
If the question only ever touches one database, stitching adds a join surface for no benefit. Reach for it when a genuine question spans sources: revenue by support tier, where revenue and tier live in different systems.