Notifications and Activity Feed

Overview of Remembrance and Awareness

In a high-velocity engineering organization, the primary challenge is not the generation of information, but the preservation of organizational judgment. Hopsule is designed to ensure that every critical decision and its underlying reasoning remains visible and enforceable across the entire team. The Notifications and Activity Feed system serves as the central nervous system for this awareness, providing real-time visibility into how the collective memory of the team is evolving. By surfacing changes to decisions, new memories, and potential contradictions, Hopsule ensures that enforcement is an act of remembrance rather than an exercise in control.

Staying informed through Hopsule allows engineering leaders and developers to maintain a shared context without the need for manual status updates or fragmented communication. Whether you are working within the Hopsule Dashboard, executing commands via the Hopsule CLI, or writing code in Hopsule for VS Code, the notification system keeps the team aligned with the current state of governance. This section provides a comprehensive guide to managing your alerts, navigating the activity feed, and utilizing the immutable audit trail for organizational transparency.

The Activity Feed: A Chronological Record of Judgment

The Activity Feed is a comprehensive, chronological log of every action taken within a project or organization. Unlike traditional logs that focus on system events, the Hopsule Activity Feed focuses on the evolution of decisions and the accumulation of memories. It provides a narrative of how a project’s governance has changed over time, allowing team members to see who accepted a decision, when a memory was appended, or why a particular Context Pack was transitioned to a frozen state.

Every entry in the Activity Feed is designed to provide full traceability. When a developer views the feed in the Hopsule Dashboard, they can see the specific entity affected, the user who performed the action, and a direct link to the relevant decision or memory. This transparency is vital for maintaining the integrity of the decision-making process, ensuring that no change to the team's shared context occurs in isolation.

Tip: You can access the global Activity Feed from the main sidebar of the Hopsule Dashboard to see a bird's-eye view of all projects, or navigate to a specific project's page to see a localized history of its governance changes.

Filtering and Navigating the Feed

As organizations grow, the volume of activity can become significant. To maintain clarity, Hopsule provides robust filtering capabilities within the Hopsule Dashboard. Users can isolate specific types of events to focus on what matters most to their current role. Filtering options include:

• Action Type: Filter by creation, state changes (e.g., Pending to Accepted), deprecations, or memory additions.

• User: View actions performed by specific team members to understand the distribution of decision-making authority.

• Entity: Narrow the feed down to specific Decisions, Memories, or Capsules.

• Date Range: Audit changes that occurred during a specific sprint, quarter, or architectural review period.

Notification Types and Triggers

Hopsule categorizes notifications based on their impact on the team's shared context. These triggers are designed to alert the right people at the right time, preventing the loss of context and ensuring that enforceable constraints are respected. By understanding these categories, teams can better configure their governance workflows.

Conflict Detection and Hopper Alerts

One of the most critical notification types is the Conflict Detection alert. Hopper, the Hopsule AI assistant, continuously monitors the relationship between new entries and the existing body of accepted decisions. If a team member drafts a decision that contradicts a previously accepted governance rule, Hopper will trigger a conflict notification. This alert does not block the user but serves as a vital advisory warning, reminding the team of their existing commitments. These alerts are surfaced in the Hopsule Dashboard and are also visible to developers using Hopsule for VS Code or Hopsule MCP, ensuring that context is preserved across all interfaces.

Important: Hopper is strictly advisory. It identifies potential contradictions based on your team's unique memories and decisions, but it never makes or enforces decisions autonomously. The final judgment always rests with the human team members.

Delivery Channels and Preferences

Hopsule ensures that you stay informed regardless of your current workflow. Notifications are delivered through multiple channels, allowing for both immediate action and long-term reflection. You can customize how and when you receive these alerts through the User Settings in the Hopsule Dashboard.

In-App Notifications

Within the Hopsule Dashboard, the notification bell icon provides a real-time count of unread alerts. Clicking this icon opens the notification panel, where you can view a summary of recent events, mark them as read, or navigate directly to the affected decision. For developers, these notifications are also integrated into the Hopsule CLI via the interactive TUI and surfaced as non-intrusive warnings in Hopsule for VS Code when a coding pattern contradicts an accepted decision.

Email Notification Preferences

To prevent notification fatigue while ensuring that critical updates are never missed, Hopsule offers flexible email delivery schedules. Users can choose the frequency that best suits their level of involvement in project governance:

1. Immediate: Receive an email the moment a notification is triggered. Recommended for project leads and those responsible for decision enforcement.

2. Daily Digest: A single summary email sent at the end of the day, grouping all activity, decision changes, and memories into a readable format.

3. Weekly Summary: A high-level overview of organizational judgment changes over the past seven days, ideal for CTOs and VPs of Engineering.

4. Custom Mentions Only: Only receive emails when you are explicitly @mentioned in a decision or memory.

Tip: If you are managing multiple organizations, you can set different email preferences for each one, allowing you to stay highly responsive to core projects while receiving digests for secondary ones.

The Immutable Audit Trail

For enterprise organizations and teams with strict compliance requirements, Hopsule provides an Immutable Audit Trail. This is a specialized view of the Activity Feed that is designed for governance and accountability. Unlike a standard activity log, the audit trail is append-only and cryptographically linked to ensure that the history of decisions cannot be altered or deleted. Organizations forget, but Hopsule remembers—and the audit trail is the ultimate proof of that remembrance.

The audit trail captures not just the change, but the full context of the change, including the state of the decision before and after the action, the specific memory entries linked to the change, and the authorization level of the user who performed it. This record is essential for SOC 2 readiness and internal post-mortems, providing a clear map of how the organization arrived at its current architectural and procedural state.

Collaboration through @Mentions and Comments

Governance is a collaborative process. Hopsule facilitates this through @mentions and comments within decisions and memories. When a team member is mentioned, they receive an immediate notification across their active channels. This is particularly useful during the Pending state of a decision, where specific stakeholders need to provide their expertise before a decision is Accepted.

Comments in Hopsule are treated as part of the decision's history. While they are not "decisions" themselves, they often contain the reasoning that eventually becomes a Memory. By notifying the right people during these discussions, Hopsule ensures that the reasoning process is inclusive and well-documented. All @mentions and comments are indexed and searchable, making it easy to find past discussions that led to major organizational shifts.

Subscription Management

To maintain a high signal-to-noise ratio, Hopsule allows users to manage their subscriptions at a granular level. You are not forced to receive notifications for every change in the organization. Instead, you can "Watch" specific entities to stay informed about their evolution.

• Project Subscription: Automatically receive notifications for all decision lifecycle changes and new memories within a specific project.

• Decision Subscription: Follow a specific decision to see when it is updated, deprecated, or when new reasoning is appended to its memories.

• Capsule Subscription: Stay informed when a Context Pack is updated or frozen, ensuring your portable context remains current.

You can manage these subscriptions directly from the Hopsule Dashboard or by using the hopsule watch command in the Hopsule CLI. This level of control ensures that every notification you receive is relevant to your work and your responsibilities within the team's governance structure.

For further information on how decisions are structured and enforced, please refer to the Decision Management and Memory Preservation documentation pages. For technical integration of notifications into your own workflows, see the Hopsule API reference.