Skip to main content

Glossary

Context Packs

Context Packs keep useful project context portable: constraints, references, approved boundaries, and evidence can travel without collapsing back into one fragile prompt.

Portable context Approved boundaries Reusable references Workflow-safe

Working definition

Context Packs package the constraints and references that should travel with the work so teams do not have to reconstruct workflow truth from scratch every session.

Definition

What goes into a Context Pack

Task-relevant constraints such as format, brand, continuity, or policy boundaries.
References and prior approved decisions that should influence the next step.
Structured context that can move across products and models without starting from zero.

Why prompt-only breaks

Why prompt-only workflows drift

Prompt-only workflows flatten context into text that is easy to lose, reinterpret, or overfit to one vendor.
Teams end up rebuilding the same operating rules every session.
As tools and models change, consistency breaks because the underlying context model was never portable.

In C

How Context Packs fit into C

Platform keeps project truth and portable context separate from any one assistant session.
Sense and Model Router use that context to scope tasks more reliably.
Studio, StageGraph, and VPS can exchange structured context instead of treating each surface as a reset point.

Related pages

Continue into portability and governance

Context Packs matter when workflows need to stay stable as teams, tools, and models change.

Platform

Platform overview

See where project truth, governed execution, and portable context live.

Explore Platform

Comparison

Context Packs vs prompt-only workflows

See the operational difference between portable context and repeated prompt reconstruction.

Read comparison

Update

Context Packs update

Read the product note behind the term.

Read update

Portability briefing

Need to map portable context to your workflow?

The practical discussion is usually about what should travel, what should stay scoped, and how to avoid rebuilding context from scratch in every session.