Understanding the Activity Feed and Audit Trail

The Activity Feed and Audit Trail serve as the central nervous system of Hopsule, providing a transparent and immutable record of how organizational judgment evolves over time. This article explores how engineering leaders and developers can leverage these tools to maintain total traceability, ensure governance, and understand the historical context of every decision and memory within their projects.

By monitoring these feeds, teams can move beyond mere information storage and embrace true remembrance. Whether you are tracking the lifecycle of a critical architectural decision or auditing the movement of context packs across organizational boundaries, the Hopsule Dashboard provides the visibility required to maintain high-integrity engineering standards.

Prerequisites

Before you begin exploring the Activity Feed and Audit Trail, ensure you meet the following requirements:

• An active Hopsule account with access to at least one project.

• Appropriate role-based permissions (Member, Admin, or Owner). Note that advanced Audit Trail exports and organization-wide views are reserved for Admin and Owner roles.

• Access to the Hopsule Dashboard via a supported web browser.

• If you are using the Hopsule CLI or Hopsule for VS Code, ensure you are authenticated so your local actions are correctly attributed in the remote feed.

The Activity Feed: Real-Time Contextual Awareness

The Activity Feed is a real-time stream of events that captures the pulse of your engineering organization. Unlike traditional logs, the Activity Feed is designed to surface changes in Decisions, Memories, and Context Packs with rich metadata and links to the underlying reasoning.

Navigating to the Activity Feed

1. Log in to the Hopsule Dashboard.

2. Select your project from the sidebar or the project switcher in the top navigation bar.

3. Click on the Activity tab located in the main navigation menu.

4. By default, you will see a chronological list of all recent actions performed within the project, starting with the most recent.

Understanding Activity Types

The feed categorizes actions to help you quickly identify the nature of a change. Every entry in the feed is linked to a specific entity, allowing you to jump directly to the relevant decision or memory.

• Decision Lifecycle Events: These events trigger whenever a decision changes state. You will see entries for Drafted, Pending, Accepted, and Deprecated. For example, when a senior engineer accepts a decision, the feed will record the transition and link to the Knowledge Graph to show how this change affects related decisions.

• Memory Append Events: Since memories in Hopsule are append-only and never deleted, the feed records every new memory entry. This ensures that the "Why" behind a decision is never lost and remains traceable to the individual contributor.

• Capsule Transitions: When a Context Pack (Capsule) moves from Active to Frozen or Historical, the feed documents this shift. This is critical for understanding which sets of decisions were active during specific project milestones.

• Hopper Suggestions: While Hopper (the built-in AI assistant) never makes decisions autonomously, it does generate drafts and suggestions. These suggestions appear in the activity feed as advisory events, providing a record of the AI’s contribution to the team’s deliberation process.

Filtering and Searching the Feed

In large engineering organizations, the volume of activity can be significant. The Hopsule Dashboard provides granular filtering tools to help you find specific events:

1. Locate the Filter button at the top-right of the Activity Feed.

2. Select Filter by User to see actions performed by a specific team member. This is useful for code reviews or performance evaluations.

3. Select Filter by Entity to isolate events related to a specific Decision, Memory, or Capsule.

4. Select Filter by Action to search for specific lifecycle changes, such as all decisions that were Deprecated in the last 30 days.

5. Use the Date Range picker to view activity from a specific sprint or development cycle.

The Audit Trail: Governance and Accountability

While the Activity Feed is for daily awareness, the Audit Trail is designed for long-term governance, security, and compliance. It is an immutable, cryptographically signed record of every interaction with the Hopsule system, including administrative changes and API access via the Hopsule API.

Accessing the Audit Trail

For security reasons, the Audit Trail is located within the organization settings and is accessible primarily to administrators.

1. In the Hopsule Dashboard, click on your organization name in the bottom-left corner.

2. Select Settings from the popup menu.

3. Click on the Audit Trail tab under the Governance section.

4. Here, you can view a high-level summary of system-wide events, including login attempts, permission changes, and token generation for the Hopsule CLI.

Audit Trail vs. Activity Feed

It is important to distinguish between these two surfaces to use them effectively:

Exporting Data for Compliance

For organizations undergoing SOC 2 audits or other compliance certifications, Hopsule allows for the export of the Audit Trail.

1. Navigate to the Audit Trail section in Organization Settings.

2. Click the Export Log button.

3. Choose your preferred format (JSON or CSV).

4. Select the time period and the categories of events you wish to include.

5. Click Generate Export. The system will prepare a secure download link, which will be sent to your registered email address.

Integration with Product Surfaces

Hopsule’s philosophy of "Enforcement is remembrance" means that the activity you see in the dashboard is often generated by developers working in their local environments.

Hopsule CLI and VS Code Activity

When a developer uses the Hopsule CLI to accept a decision (e.g., hopsule decision accept [ID]), this action is instantly synchronized with the Hopsule Dashboard. The Activity Feed will display the event and note that it originated from the CLI. Similarly, if a developer acknowledges a decision conflict within Hopsule for VS Code, that acknowledgment is recorded as a memory entry, preserving the reasoning for why a specific constraint was bypassed or modified.

Hopsule MCP and AI Agents

When using the Hopsule MCP (Model Context Protocol) to connect external AI agents (like Claude or Cursor) to your team’s memory, the Audit Trail tracks every read request made by the agent. This ensures you have a clear record of which AI tools are accessing your organizational context, maintaining the principle that AI agents are read-only and cannot mutate decisions without human intervention.

The Knowledge Graph and Activity Visualization

The Knowledge Graph (also known as the Brain) in the Hopsule Dashboard provides a visual representation of how activities impact your project's structure. When a decision is accepted, you can watch the graph update in real-time. The Activity Feed provides the "When" and "Who," while the Knowledge Graph provides the "How" by showing the relationships and dependencies created by that activity.

Tips and Best Practices

• Review the Feed Weekly: Engineering leads should review the Activity Feed during weekly syncs to identify any drift in decision-making or to highlight important new memories that the whole team should be aware of.

• Use Detailed Commit Messages: When accepting a decision via the Hopsule CLI, always include a brief summary of the reasoning. This text will appear in the Activity Feed and become a permanent part of the project’s memory.

• Monitor Hopper Suggestions: Keep an eye on the feed for Hopper suggestions. If the AI is frequently drafting decisions that are later rejected, it may indicate that your existing memories need more detail to provide better context for the AI.

• Leverage Tags: Categorize your decisions with tags. You can then filter the Activity Feed by these tags to see how specific areas of your architecture (e.g., #security, #frontend) are evolving.

• Audit Token Usage: Regularly check the Audit Trail for the creation of new Hopsule API tokens or CLI sessions to ensure that access is limited to authorized personnel only.

Troubleshooting

Related Articles

• Managing the Decision Lifecycle: From Draft to Deprecated

• Creating and Sharing Context Packs (Capsules)

• Securing Your Hopsule Organization with Role-Based Access Control