Task Management with Kanban Board

Overview of the Decision Pipeline

The Hopsule Dashboard provides a visual governance interface known as the Kanban board. Unlike traditional project management tools that focus on generic tasks, the Hopsule Kanban board is specifically engineered to manage the lifecycle of organizational decisions. It serves as the primary workspace for engineering leaders and teams to shepherd a decision from its initial conception as a Memory or Draft through to its final state as an enforceable constraint within the Hopsule for VS Code environment. By visualizing the decision pipeline, organizations can ensure that no critical architectural choice or procedural agreement is lost in the noise of daily operations.

At its core, the Kanban board represents the philosophy that enforcement is a form of remembrance. Every card on the board is a potential Decision that carries with it the weight of the team's collective judgment. As these cards move across the board, they gain context, undergo rigorous review, and eventually become part of the organization's permanent memory. This visual transition ensures that the reasoning behind every choice is preserved and that the transition from a "good idea" to a "mandatory standard" is transparent and deliberate.

Accessing the Kanban Board

To access the Kanban board, navigate to the Hopsule Dashboard and select the Board icon from the primary sidebar navigation. By default, the board displays the decision pipeline for your current active project. However, the interface allows for rapid context switching between different organizations and projects using the global selector at the top of the screen. This ensures that engineering leaders can maintain a high-level overview of multiple workstreams while senior developers can focus on the specific decisions affecting their immediate technical domain.

The board is designed to work in tandem with other Hopsule features. For instance, a decision drafted by Hopper, our built-in AI assistant, will automatically appear in the Draft column, ready for human refinement. Similarly, any changes made to a decision's state via the Hopsule CLI will be reflected on the board in real-time, providing a synchronized source of truth across all product surfaces.

Understanding the Default Decision Lifecycle

Hopsule utilizes a standardized set of columns to represent the lifecycle of a decision. These stages are not merely status labels; they define the functional behavior of the decision across the entire Hopsule ecosystem, including how Hopsule MCP presents context to AI agents and how Hopsule for VS Code surfaces warnings to developers.

Important: A decision only becomes an enforceable constraint once it is moved into the Accepted column. At this moment, the decision is synchronized with Hopsule for VS Code, where it will begin triggering warnings or notifications if developer code contradicts the agreed-upon standard. This ensures that the transition from discussion to enforcement is a conscious, visible action taken on the Kanban board.

Managing Decisions via Drag-and-Drop

The Kanban board allows for intuitive state management through drag-and-drop interactions. Moving a decision card between columns updates its lifecycle status globally. For example, dragging a card from In Discussion to Accepted triggers an immediate update to the Knowledge Graph and notifies all relevant team members via the activity feed. This physical movement of cards represents the transition of organizational judgment from a state of flux to a state of committed governance.

When a card is moved to Accepted, the Hopsule Dashboard may prompt the user to finalize the decision's metadata, such as its primary tags or the specific Context Pack it belongs to. This ensures that the decision is properly categorized for future retrieval. Conversely, moving a card to Deprecated does not delete the entry; instead, it preserves the decision as a Memory, ensuring that the reasoning behind the original choice remains accessible even after the decision is no longer enforced.

Task Management and Sub-tasks

Decisions often require a series of preparatory steps before they can be fully accepted or implemented. Hopsule allows users to add Tasks and Sub-tasks directly to any decision card. These tasks might include "Conduct benchmark testing," "Review with security team," or "Update internal documentation." By nesting these tasks within the decision itself, Hopsule maintains a clear link between the administrative work and the technical choice it supports.

1. Click on any decision card to open the Decision Detail View.

2. Locate the Tasks section and click Add Task.

3. Enter a descriptive title for the task and hit enter.

4. To add further granularity, select a task and choose Add Sub-task.

5. Mark tasks as complete as the decision progresses through the pipeline.

These tasks are visible to all team members, providing transparency into what is required to move a decision from Pending Review to Accepted. This prevents "decision stall," where architectural choices remain in limbo because the necessary validation steps are unclear or unassigned.

Assigning Responsibility and Collaboration

Accountability is a cornerstone of effective governance. On the Kanban board, you can assign specific team members to decision cards or individual tasks. Assigning an Author or a Reviewer ensures that there is a clear point of contact for the reasoning behind a decision. This is particularly important for large engineering organizations where the person who proposed a decision may not be the same person responsible for its final approval.

To assign a team member, click the Assignee icon on the card or within the detail view. You can search for members by name or role. When a member is assigned, they receive real-time notifications of any updates, comments, or state changes associated with that decision. This collaborative layer ensures that Memories are captured from all relevant perspectives before a decision is finalized.

Tip: Use assignments to designate "Decision Owners" who are responsible for maintaining the health and relevance of specific Context Packs as the project evolves.

Advanced Filtering and Search

As an organization grows, the number of decisions and memories can become vast. The Kanban board includes powerful filtering tools to help you find the specific context you need. You can filter the board by Tag, Author, Priority, or Context Pack. This allows a team lead to see only the "High Priority" decisions currently in the Pending Review column, or a developer to see all decisions they are currently Assigned to across all projects.

• Tag Filtering: View decisions related to specific domains like "Security," "Performance," or "API Design."

• Author Filtering: Track the contributions of specific team members to the organizational memory.

• Priority Filtering: Focus on the most critical architectural changes that require immediate attention.

• Context Pack Filtering: Isolate decisions that belong to a specific portable bundle or Capsule.

The search bar at the top of the board also allows for full-text search across decision titles, descriptions, and linked memories. This ensures that even if you don't remember where a decision sits in the lifecycle, you can find it instantly by searching for keywords related to its reasoning.

Due Dates and Review Reminders

To prevent the accumulation of "stale" decisions, Hopsule supports Due Dates and Reminders. When creating or editing a decision card, you can set a target date for its review or acceptance. If a decision remains in a non-final state (like Pending Review) past its due date, the Hopsule Dashboard will highlight the card and notify the assignees.

This feature is vital for maintaining an active and accurate Memory System. It encourages teams to regularly revisit In Discussion items and either move them to Accepted or move them to Deprecated if they are no longer relevant. By setting reminders, engineering leaders can ensure that the decision pipeline remains fluid and that the organization's governance stays in sync with its actual development velocity.

Customizing Board Views and Workflows

While Hopsule provides a robust default workflow, we recognize that every engineering organization has unique processes. The Kanban board can be customized to reflect these nuances. Users with administrative privileges can add, rename, or reorder columns to better match their internal review cycles. For example, a team might add a "Security Audit" column between Pending Review and Accepted to ensure that all decisions undergo a mandatory security check.

Additionally, the board supports multiple Views:

• Project View: The standard view showing all decisions within a specific project.

• Team View: Aggregates decisions across multiple projects that are assigned to a specific team.

• Personal View: A focused view showing only the decisions and tasks assigned to the current user.

These views allow users to toggle between a broad organizational perspective and a narrow, task-oriented focus without losing the underlying context of the Decision & Memory Layer.

Integration with the Knowledge Graph

The Kanban board is not a siloed feature; it is a visual representation of the data that powers the Knowledge Graph (also known as the Brain). Every time a card is moved or a task is completed, the Knowledge Graph updates to reflect the new state of the organization's memory. While the Kanban board provides a linear, process-oriented view, the Knowledge Graph provides a relational view, showing how an Accepted decision in one column might be linked to multiple Memories or Context Packs elsewhere in the system.

By using the Kanban board to manage the "now" and the Knowledge Graph to visualize the "always," engineering teams can achieve a complete understanding of their technical landscape. This synergy ensures that every decision is not just a point in time, but a permanent, traceable, and enforceable part of the organization's identity.