Skip to content
Glossary

Vertical Pack

A vertical pack is an optional packaged configuration that tailors Threada primitives to a specific domain of work — its intents, extraction fields, evidence sources, policies, and actions. Packs help a team start faster without replacing the underlying primitive workspace.

Synonyms: pack, vertical pack, solution pack, domain pack

A vertical pack turns shared work-automation primitives into a focused starting configuration for one domain. Instead of configuring intents, extraction, evidence, policy, and actions from scratch, a team can adopt a pack that already encodes sensible defaults for a workflow like procurement or incident response. Packs accelerate launch while remaining fully editable, but they are not required before the primitive workspace is useful. Because each pack composes the same primitives, multiple packs can run side by side over shared, governed infrastructure.

Frequently asked questions

What does a vertical pack configure?
The intents it recognizes, the fields it extracts, the evidence it grounds answers in, the approval policies it enforces, and the governed actions it can propose for that domain of work.
Can packs be customized?
Yes. A pack is an optional starting configuration that teams adapt in Studio — adjusting intents, prompts, evidence sources, and policies — while the underlying primitives remain directly configurable.