What Are Context Packs (Capsules)?

Context Packs, frequently referred to as Capsules, represent the primary unit of portability and governance within the Hopsule ecosystem. This guide provides a comprehensive overview of how to create, manage, and deploy these bundles of organizational judgment to ensure that your team's decisions and memories are preserved across projects, time, and AI sessions. By mastering Context Packs, you enable a seamless flow of context that empowers both human developers and AI agents to operate with full awareness of established constraints and reasoning.

The philosophy behind Context Packs is simple: enforcement is remembrance, not control. When a team member or an AI agent interacts with a Capsule, they are not being restricted by arbitrary rules; rather, they are being provided with the collective memory of the organization. This article will walk you through the lifecycle of a Capsule, from its initial drafting in the Hopsule Dashboard to its enforcement within Hopsule for VS Code and its consumption by AI agents via Hopsule MCP.

Prerequisites

Before you begin creating and managing Context Packs, ensure you have the following in place:

• An active Hopsule account with access to the Hopsule Dashboard.

• At least one Accepted Decision or Memory already created within your project.

• The Hopsule CLI installed if you intend to manage Capsules via the terminal.

• Appropriate permissions (Maintainer or Admin) to create and share organizational context.

Understanding the Anatomy of a Capsule

A Context Pack is more than a simple folder or a collection of links. It is a structured, versioned, and enforceable bundle of two core entities: Decisions and Memories. Decisions provide the explicit commitments and constraints that the team has agreed to follow, while Memories provide the persistent, append-only context that explains the reasoning and history behind those decisions. Together, they form a complete picture of organizational judgment.

Capsules are designed to be portable. This means a Capsule created for a core infrastructure project can be "plugged into" a new microservice project, immediately bringing the new team up to speed on architectural standards, security protocols, and historical lessons learned. This portability is what allows Hopsule to function as a true memory layer for engineering organizations.

Creating and Managing Capsules in the Hopsule Dashboard

The Hopsule Dashboard is the central hub for orchestrating your Context Packs. Follow these steps to create your first Capsule:

1. Log in to the Hopsule Dashboard and navigate to the Context Packs section in the primary sidebar.

2. Click the Create Capsule button located in the top-right corner of the interface.

3. In the General Information pane, provide a clear, authoritative name for your Capsule (e.g., "Production Security Standards v1").

4. Enter a detailed description. This should explain the purpose of the Capsule and the specific context it is intended to preserve.

5. Navigate to the Decisions tab within the creation wizard. Here, you will see a list of all available decisions. Click the Add to Capsule button next to each decision you wish to include. You can filter by tags or category to find relevant decisions quickly.

6. Move to the Memories tab. Select the append-only entries that provide the necessary "why" for the decisions you included. Memories are crucial for providing the nuance that raw decisions might lack.

7. Review the Knowledge Graph (also known as the Brain) visualization at the bottom of the page to see how your selected decisions and memories relate to one another. This helps identify if any critical context is missing.

8. Click Save Draft to finalize the initial setup.

The Capsule Lifecycle

Context Packs follow a strict lifecycle to maintain the integrity of organizational governance. Understanding these states is essential for effective context management:

• Draft: The Capsule is being assembled. It is not yet visible to Hopsule MCP or Hopsule for VS Code. This is the stage for refinement and internal review.

• Active: The Capsule is live. It is actively being used by Hopper for suggestions and by Hopsule for VS Code for real-time enforcement. AI agents connected via Hopsule MCP can now read these decisions.

• Frozen: The Capsule is locked for historical preservation. No further decisions or memories can be added or removed. This is ideal for archiving the state of context at a specific milestone, such as a major release or an audit.

• Historical: The Capsule is no longer used for active enforcement but remains searchable and accessible for research and remembrance. This ensures that even as the organization evolves, the reasoning of the past is never lost.

To transition a Capsule between states, open the Capsule in the Hopsule Dashboard and use the Status dropdown menu in the header. Note that moving a Capsule to the Frozen state is irreversible to ensure the integrity of the record.

Using the Hopsule CLI for Capsule Management

For developers who prefer to stay in the terminal, the Hopsule CLI provides powerful commands for interacting with Context Packs. This is particularly useful for CI/CD integrations or quick context checks during development.

1. To view all available Capsules, use the command: hopsule capsule list. This will display an interactive TUI (Terminal User Interface) listing names, versions, and current statuses.

2. To create a new Capsule from the terminal, use: hopsule capsule create --name "API Standards". This will open an interactive prompt where you can select decisions and memories to include.

3. To inspect the contents of a specific Capsule, use: hopsule capsule inspect [CAPSULE_ID]. This provides a detailed breakdown of all linked decisions and the associated reasoning preserved in memories.

4. To sync a Capsule to your local environment for use in offline workflows, use: hopsule capsule pull [CAPSULE_ID].

Enforcement and Consumption

Once a Capsule is Active, its power is realized through Hopsule's various product surfaces. Here is how the context is enforced and consumed:

Hopsule for VS Code

The IDE extension is where enforcement becomes tangible. When you open a project associated with an Active Capsule, Hopsule for VS Code scans your workspace. If a developer writes code that contradicts an Accepted Decision within that Capsule, a warning is surfaced directly in the editor. This is not about control; it is about the system "remembering" the team's agreement and bringing it to the developer's attention at the moment it matters most.

Hopsule MCP (Model Context Protocol)

For teams using AI agents (such as Cursor or Claude), Hopsule MCP acts as the bridge. It provides a read-only stream of the decisions and memories contained within your Active Capsules to the AI. This ensures the AI agent is context-aware, preventing it from suggesting patterns that violate organizational standards. The AI becomes a partner in governance, guided by the authority of your Context Packs.

Hopper (The AI Assistant)

Within the Hopsule Dashboard, Hopper uses your Capsules as the primary source of truth for its RAG (Retrieval-Augmented Generation) capabilities. You can ask Hopper, "Why do we use this specific authentication pattern?" and Hopper will query the memories linked in your Capsules to provide an insightful, context-rich explanation based on your organization's actual history.

Sharing Context Packs via Secure Tokens

Hopsule allows you to share Capsules across different organizations or with external partners without compromising your entire workspace. This is done via Secure Sharing Tokens.

1. Open the desired Capsule in the Hopsule Dashboard.

2. Navigate to the Sharing tab.

3. Click Generate Token. You can set an expiration date for the token to ensure temporary access.

4. Copy the generated token and provide it to the recipient.

5. The recipient can then use the Hopsule CLI or Hopsule Dashboard to "Import Capsule" using that token. This creates a read-only link to your context, ensuring they stay updated as you append new memories to the Capsule.

Tips and Best Practices

• Granularity Matters: Avoid creating a single "Master Capsule" for the entire company. Instead, create smaller, focused Context Packs for specific domains (e.g., "Frontend Performance," "Data Privacy," "Cloud Infrastructure"). This makes enforcement more relevant and less noisy.

• Layer Your Context: Use multiple Capsules simultaneously. A project might subscribe to a "Global Security" Capsule, a "Company-wide Architecture" Capsule, and a project-specific "Mobile App" Capsule. Hopsule handles the overlapping context automatically.

• Leverage the Append-Only Nature: When a decision is challenged or modified, do not delete the old reasoning. Append a new Memory to the Capsule explaining the change. This creates a traceable audit trail of organizational evolution.

• Use Hopper for Conflict Detection: Before moving a Capsule from Draft to Active, ask Hopper to "Analyze this Capsule for contradictions." Hopper will look for decisions that might conflict with each other, allowing you to resolve them before they impact the development team.

• Regularly Freeze Milestones: At the end of every major project phase, create a Frozen Capsule. This serves as a permanent record of the governance state at that time, which is invaluable for compliance and post-mortem analysis.

Troubleshooting

If you encounter issues while working with Context Packs, refer to the following table for common causes and solutions.

Related Articles

• Managing the Decision Lifecycle: From Draft to Accepted

• Preserving Reasoning with Append-Only Memories

• Setting Up Hopsule MCP for AI Agent Awareness

• Real-time Enforcement with Hopsule for VS Code

By effectively utilizing Context Packs, your organization moves away from the "tribal knowledge" trap and toward a system of robust, portable governance. Remember that the goal of Hopsule is to ensure that every decision made today remains a part of the organization's memory tomorrow. Capsules are the vessels that make this remembrance possible, providing the authority and context necessary for engineering excellence.