Documentation / QueryTek Tapestry glossary / QueryTek Tapestry
QueryTek Tapestry™ is the interoperability product in the QueryTek family. It connects enterprise partner systems through one identity model and one governed routing layer, so eligibility, organizational scope, and progress travel with a person across tools instead of being re-established at every boundary.
Tapestry addresses a specific and expensive problem: workforce programs span HR systems, learning platforms, and partner tools, and the context that makes work governable rarely survives the crossing. Each integration ends up re-implementing who the user is, which organization they belong to, and what they are entitled to — with slightly different answers.
Three capabilities define the product.
One identity model. Rather than each connection resolving identity its own way, integrations share a single model of who is acting and which organization they act on behalf of. This is what makes a handoff between two partner systems attributable rather than anonymous.
Governed routing. Movement between systems passes through a routing layer that applies policy rather than point-to-point connections that each encode their own rules. Adding a partner is a registration rather than a new integration project, and the policy that governs the movement lives in one place.
Context propagation. Eligibility, organizational scope, and progress travel with the request. Without this, each system holds a partial view and reconciliation becomes a recurring operational task rather than a design property.
The alternative — bilateral integrations between every pair of systems — grows quadratically and distributes governance across connections nobody owns. That is the integration tax Tapestry is built to remove.
Tapestry uses shared QueryTek platform tenancy and API foundations rather than defining its own, so tenant boundaries and access behaviour are the platform's concepts.
Organizations rarely lose control of information inside a system. They lose it at the boundaries, where context is dropped and each side assumes the other retained it — which is where audit gaps and eligibility errors originate.
Making the boundary a governed layer rather than a collection of bilateral connections is what turns integration from an accumulating liability into something with one place to inspect.
QueryTek Tapestry is the anchor term for the interoperability product; sibling terms in this glossary define its orchestration and registry vocabulary. Partner adapter wiring, routing configuration, and SDK paths are handled through onboarding rather than public documentation.
