Dashboard Navigation Guide

The Hopsule Dashboard serves as the centralized command center for your organization’s collective judgment and context. It is designed to provide engineering leaders and developers with a high-fidelity view of the decisions that govern their technical landscape and the memories that justify them. Understanding how to navigate this interface is essential for maintaining organizational alignment and ensuring that enforcement remains a function of remembrance rather than control.

This guide provides an exhaustive walkthrough of the Hopsule Dashboard, covering every interface element from the high-level Knowledge Graph to the granular details of decision lifecycle management. By the end of this article, you will be equipped to manage context packs, interact with Hopper, and configure the necessary tokens for Hopsule CLI and Hopsule MCP integrations.

Prerequisites

Before exploring the Hopsule Dashboard, ensure you have completed the following requirements:

• An active Hopsule account associated with an organization or project.

• Verified email address for administrative access to organization settings.

• Appropriate role-based access permissions (Member, Admin, or Owner) to view or modify specific project entities.

• A basic understanding of the Hopsule philosophy: Decisions are enforceable commitments, and Memories are the persistent reasoning behind them.

The Global Sidebar: Your Primary Navigation Hub

The sidebar on the left-hand side of the Hopsule Dashboard is the primary method for switching between different functional areas of the platform. It is divided into several distinct sections that reflect the core entities of the Hopsule ecosystem.

1. Organization and Project Switcher: Located at the very top of the sidebar, this dropdown allows you to toggle between different organizations and specific projects. Selecting a project filters all subsequent views—Decisions, Memories, and Capsules—to only show context relevant to that specific scope.

2. Dashboard Home: The default landing page. It provides a "Pulse" view of your project, including recent activity, pending decisions requiring review, and quick statistics on decision health.

3. Decisions: This is where you manage the enforceable commitments of your team. Clicking this will take you to the Decision Management view, where you can see the lifecycle of your project's governance.

4. Memories: Access the append-only log of your organization's reasoning. This view is dedicated to the "Why" behind your technical evolution.

5. Context Packs (Capsules): Manage the portable bundles of decisions and memories that you share across projects or with AI agents via Hopsule MCP.

6. The Brain (Knowledge Graph): A visual representation of how your decisions and memories interconnect. It allows you to see the ripple effects of a single decision across your entire organization.

7. Activity Feed: A real-time audit trail of every change made within the project, from decision state transitions to new memory entries.

Decision Management: Governing the Engineering Lifecycle

The Decisions view is the most critical part of the Hopsule Dashboard. It is where "remembrance" is turned into "enforcement." Decisions in Hopsule are not static documents; they are living entities with a specific lifecycle.

To create a new decision, click the Create Decision button in the top-right corner of the Decisions view. This opens a modal where you must define the decision title, category, and initial reasoning. Once created, a decision enters the Draft state.

Within the Decisions view, you can toggle between two primary layouts:

• List View: A dense, searchable table ideal for high-volume review and bulk actions. You can filter by tags, authors, or current state.

• Kanban View: A visual board that organizes decisions by their lifecycle stage: Draft, Pending, Accepted, and Deprecated. This is the preferred view for engineering leaders to track the progress of new governance proposals.

To move a decision through its lifecycle, you can drag and drop cards in the Kanban view or use the Update State dropdown within the individual decision detail page. Note that once a decision is moved to Accepted, it becomes active for enforcement in Hopsule for VS Code and Hopsule CLI.

Memory Preservation: The Append-Only History

Memories in Hopsule represent the persistent context that informs your decisions. Unlike other systems where information can be overwritten or deleted, Hopsule Memories are append-only. This ensures that the historical reasoning of the organization is never lost, even as people and projects change.

When you navigate to the Memories section, you are presented with a chronological feed of context entries. Each entry is linked to a specific decision or project. To add a new memory, click the Add Memory button. You will be prompted to provide the context and link it to an existing decision if applicable. This traceability is what allows Hopper and other AI tools to provide accurate, context-aware suggestions.

The search bar in the Memories view is optimized for natural language. Instead of searching for keywords, you can search for concepts like "Why did we move away from monolithic architecture?" Hopsule will surface the relevant memory entries that contain the organizational judgment you are looking for.

The Knowledge Graph (The Brain)

The Knowledge Graph, often referred to as "The Brain," is a powerful visualization tool located in the sidebar. It maps the relationships between your Decisions, Memories, and Context Packs. In a complex engineering organization, a single decision often relies on multiple memories and affects several other decisions.

In the Knowledge Graph view, you can:

• Zoom and Pan: Navigate through large clusters of interconnected context.

• Node Highlighting: Click on a decision node to see all linked memories and dependent decisions. This is invaluable for impact analysis before deprecating an old decision.

• Filter by Type: Toggle the visibility of different entity types to reduce noise and focus on specific governance structures.

• Traceability Path: Select two nodes to see the shortest path of reasoning that connects them.

Interacting with Hopper

Hopper is the built-in AI assistant accessible from the bottom-right corner of the Hopsule Dashboard. Hopper is advisory, meaning it never makes decisions on its own but provides the context necessary for humans to make informed judgments.

When you open the Hopper interface, you can ask questions about your project's history or current constraints. For example, "What are our current decisions regarding API versioning?" Hopper will query your project's accepted decisions and memories to provide a summarized answer with citations to the original entries.

One of Hopper's most powerful features is the Draft from Chat function. If you are discussing a potential new direction with Hopper, you can click a single button to transform that conversation into a Draft Decision, which then appears in your Decisions Kanban for formal review.

Managing Context Packs (Capsules)

Context Packs, or Capsules, are the mechanism for portability within Hopsule. They allow you to bundle a specific set of decisions and memories to be shared or used in specific environments. Navigate to the Capsules section in the sidebar to manage these bundles.

Capsules have their own lifecycle:

1. Draft: The capsule is being assembled and is not yet available for external use.

2. Active: The capsule is live and can be pulled by Hopsule CLI or Hopsule MCP.

3. Frozen: The capsule is locked. No new decisions or memories can be added, ensuring a stable context for a specific point in time (e.g., a "v1.0 Architecture" capsule).

4. Historical: The capsule is no longer in active use but is preserved for long-term organizational remembrance.

To create a capsule, click New Context Pack, select the decisions and memories you wish to include, and set the initial state. You can also generate a secure Public Sharing Token from the capsule settings if you need to share this context with external partners or auditors.

Integrations and API Management

For Hopsule to be effective, it must exist where the work happens. The Settings > Integrations section of the Hopsule Dashboard is where you manage the connections to your development environment.

• Hopsule CLI: Generate personal access tokens to authenticate your terminal sessions. This allows you to accept or deprecate decisions directly from your CI/CD pipelines or local dev environment.

• Hopsule MCP: Configure the Model Context Protocol server settings. This is where you obtain the connection strings required to make your AI agents (like those in Cursor or Claude) context-aware.

• Hopsule API: For custom workflows, you can generate API keys with specific scopes. The API allows for programmatic retrieval of decisions and memories, though mutation is strictly controlled to maintain governance integrity.

• Hopsule for VS Code: While the extension is installed via the VS Code Marketplace, you link it to your dashboard via the Sync Codebase button in the project settings, which establishes the secure, local-only processing link.

Tips and Best Practices

• Enforcement is Remembrance: Use the dashboard to ensure that decisions are not just "rules" but are linked to the memories that explain them. An enforced decision without a memory is just control; an enforced decision with a memory is governance.

• Regularly Deprecate: Don't let your dashboard become cluttered with obsolete decisions. Use the Deprecate state to signal that a decision is no longer active while still preserving it in the Knowledge Graph for historical context.

• Leverage Hopper for Drafting: Instead of staring at a blank "Create Decision" screen, talk through the reasoning with Hopper first. This ensures that the initial draft is already grounded in existing organizational context.

• Use Tags Strategically: Apply consistent tags (e.g., #security, #frontend, #infrastructure) across both Decisions and Memories to make the Knowledge Graph more navigable.

• Audit the Activity Feed: Engineering leaders should review the Activity Feed weekly to stay informed of new drafts and state changes without needing to attend extra sync meetings.

Troubleshooting Navigation and Visibility

Related Articles

• Managing the Decision Lifecycle: A deep dive into moving decisions from Draft to Accepted and how to handle deprecation.

• Setting up Hopsule MCP for AI Agents: How to connect your dashboard's context to external AI tools using the Model Context Protocol.

• Creating and Sharing Context Packs: A guide on bundling organizational judgment for portable use across different engineering teams.