Creating Your Hopsule Account

Establishing your Hopsule account is the foundational step in building a resilient memory layer for your engineering organization. This process transcends simple registration; it is the act of initializing a secure environment where organizational judgment is preserved, decisions are enforced, and context is never lost to the passage of time or team turnover.

By following this guide, you will configure your Hopsule Dashboard, establish your first Context Packs, and prepare your environment for seamless integration with the Hopsule CLI, Hopsule for VS Code, and Hopsule MCP. Proper initial configuration ensures that your team’s collective authority is maintained through a robust governance system that prioritizes remembrance over mere control.

Prerequisites

Before beginning the account creation process, ensure you have the following requirements met to ensure a smooth transition into the Hopsule ecosystem:

• A professional engineering or corporate email address (Personal email addresses are supported for Solo mode, but organizational domains are recommended for team governance).

• Administrative access to your team's primary communication or identity provider if you intend to use Single Sign-On (SSO).

• A clear understanding of your organization's initial governance structure, including the primary projects that will require Context Packs.

• Access to a terminal environment if you intend to verify your account via the Hopsule CLI immediately following registration.

Main Content: Step-by-Step Account Configuration

The following steps detail the exhaustive process of creating and configuring your Hopsule account to ensure maximum context preservation and enforcement capability.

Step 1: Initial Authentication and Identity Provisioning

Navigate to the Hopsule Dashboard login page. You will be presented with several options for establishing your identity within the memory system. Hopsule supports standard email/password combinations as well as major identity providers for seamless SSO integration.

Choose your preferred method and follow the prompts. If you are the first member of your organization to join, you will automatically be designated as the primary administrator for the organizational memory layer. During this stage, Hopsule establishes your unique encryption keys. Security is a baseline guarantee; therefore, TLS 1.3 is utilized for all data in transit and AES-256 for all data at rest, regardless of your chosen plan tier.

Step 2: Defining the Organizational Memory Space

Once authenticated, you will be prompted to Create an Organization. This is the highest-level entity in Hopsule and serves as the container for all your decisions, memories, and capsules. Input your organization’s formal name and select a unique slug. This slug will be used in the Hopsule API and Hopsule CLI to reference your organizational context.

In this stage, you are not just naming a workspace; you are defining the boundaries of your governance system. You may also upload an organizational avatar to help team members quickly identify the correct context when switching between multiple organizations in the Hopsule Dashboard.

Step 3: Initializing the Knowledge Graph (The Brain)

After creating your organization, navigate to the Brain section in the left-hand navigation menu of the Hopsule Dashboard. The Brain is your Knowledge Graph—a visual representation of how your decisions and memories interconnect. For a new account, this will be empty, but initializing it now sets the stage for future traceability.

Click on Configure Graph Settings to define how relationships should be visualized. You can set default weights for different decision types and establish how Hopper, our built-in AI assistant, should suggest links between disparate memories. Remember, Hopper is purely advisory; it identifies potential contradictions and suggests connections, but the final authority always rests with the human user.

Step 4: Creating Your First Context Pack (Capsule)

Context Packs, or Capsules, are portable bundles of decisions and memories designed to survive system changes and personnel shifts. To create your first one, click the New Capsule button in the Hopsule Dashboard.

Give your Capsule a descriptive name (e.g., "Architecture Standards" or "Frontend Governance"). Set the initial state to Draft. Capsules have a lifecycle: Draft, Active, Frozen, and Historical. By starting in Draft mode, you can curate the initial memories and decisions before they are enforced across the team’s IDEs and CI/CD pipelines.

Step 5: Establishing the Initial Memory Layer

Before a decision can be made, there is usually a history of reasoning. In Hopsule, we call these Memories. Memories are append-only context entries that explain the "why" behind your engineering evolution. They are never deleted and never overwritten, ensuring a permanent audit trail of organizational judgment.

Click Add Memory within your new Capsule. Describe a recent technical challenge or a lesson learned by the team. This entry becomes a permanent part of your organizational memory, searchable and linkable to future decisions. This ensures that when a new engineer joins the team three years from now, the reasoning behind your current choices remains accessible.

Step 6: Drafting and Accepting Your First Decision

Decisions are the primary enforceable entities in Hopsule. Unlike a simple text entry, an Accepted Decision becomes a constraint that Hopsule for VS Code and the Hopsule CLI will actively monitor.

1. Navigate to the Decisions tab in the Dashboard.

2. Click Create Decision.

3. Use the editor to define the commitment. You can ask Hopper to help draft the decision based on the memories you created in the previous step.

4. Set the status to Pending for team review, or if you have the authority, move it directly to Accepted.

Once a decision is Accepted, it is live. Any code written in an environment connected via Hopsule for VS Code that contradicts this decision will trigger a warning, ensuring that enforcement is synonymous with remembrance.

Step 7: Configuring Personal Preferences and Notifications

Click on your profile icon in the bottom-left corner and select Account Settings. Here, you can configure how you receive notifications regarding decision lifecycles. Hopsule provides real-time updates for:

• New Decision Drafts

• Decision State Changes (e.g., Pending to Accepted)

• Conflict Detections identified by Hopper

• Activity Feed updates

Ensure your notification settings align with your role. Engineering leaders may want high-granularity updates, while individual contributors might prefer notifications only for decisions that impact their specific Capsules.

Step 8: Provisioning Access Tokens for Integrations

To use the Hopsule CLI, Hopsule API, or Hopsule MCP, you must generate a secure access token. Navigate to Settings > Developer Tools in the Hopsule Dashboard. Click Generate New Token, provide a description (e.g., "Local Development CLI"), and set an expiration date according to your security policy.

Copy this token immediately. Due to our commitment to security and end-to-end encryption, these tokens are not stored in plain text and cannot be retrieved once the window is closed. You will use this token to authenticate your terminal and AI agents, allowing them to become context-aware of your team's decisions and memories.

Tips and Best Practices

• Embrace the Append-Only Nature: When a decision is no longer valid, do not delete it. Change its status to Deprecated. This preserves the memory of why that decision existed and why it was eventually superseded.

• Use Hopper as a Consultant: When drafting complex decisions, use Hopper to "Search for Conflicts." Hopper will scan your existing memories and decisions to ensure your new commitment doesn't contradict established governance.

• Granular Capsules: Instead of one giant Capsule for the whole company, create specific Context Packs for different domains (e.g., Security, Infrastructure, UI Patterns). This makes the context more portable and relevant.

• Enforce Early: Install Hopsule for VS Code immediately after account setup. Seeing decisions enforced in real-time within your editor is the most effective way to internalize organizational judgment.

• Solo Mode for Personal Growth: If you are using Hopsule individually, treat it as your professional legacy. Record every major architectural pivot as a Memory to build a personal library of technical wisdom.

Troubleshooting

If you encounter issues during the account creation or initial configuration phase, refer to the table below for common causes and resolutions.

Related Articles

• Managing Organizational Governance: A deep dive into roles, permissions, and the lifecycle of an engineering decision.

• Integrating Hopsule with AI Agents: How to use Hopsule MCP to provide your AI tools with persistent organizational memory.

• Advanced Knowledge Graph Visualization: Learning to navigate the Brain to discover hidden patterns in your team's decision-making history.