Skip to content
threada Docs

Shells and packs

Threada is built as Core + Shells + Packs. This page explains the three layers and how they relate.

Core

The shared platform: identity, tenancy, the evidence pipeline, the runtime that ingests requests and produces drafts, the action engine that executes approved outcomes, audit, and governance.

Customers don’t interact with Core directly — they interact with it through a shell.

Shells

A shell is a packaged experience with its own chrome, trust posture, and audience.

ShellAudienceWhat you do here
WorkOperatorsProcess WorkItems, review queues, work in the workspace, approve governed actions, review the timeline.
StudioBuildersConfigure packs, intake channels, prompts, policies, automations, evals.
AdminIT, security, financeManage users and identity providers, billing, PII and retention policies, audit exports.
TravelTravel customersFlagship consumer-facing app on Threada’s runtime.
InvestInvest customersFlagship consumer-facing app on Threada’s runtime.

Shells share the same five interaction surfaces — intent, workspace, evidence, controls, and timeline — so the muscle memory carries between them.

Packs

A pack is the domain unit of value. It bundles everything specific to a job: intake schema, prompts, retrieval scopes, templates, approval policies, and the actions an operator can take.

Inside Work, installed packs appear as user-facing solutions with job-specific stages. Inside Studio, the same artefacts are edited as packs and workflows. The runtime is identical; only the labels and chrome differ.

You can:

  • Install a pack from the catalog and configure required variables.
  • Build a pack from scratch in Studio.
  • Version a pack and roll back to a previous published version if a release misbehaves.

How they compose

  customer request
        │
        ▼
   channel intake  ──►  normalized WorkItem
                              │
                              ▼
                         routing rules
                              │
                              ▼
                    pack-defined workflow
                       │           │
                       ▼           ▼
                   evidence     action engine
                       │           │
                       ▼           ▼
                       └──► reviewed draft ──► approved? ──► execute

Every step is auditable; every decision links back to evidence; every action is governed by the pack’s policy. The shell determines who sees what; the pack determines what happens.