Skip to main content

The Workspace: Your Integrated Product Environment

The Masterminds platform is an Integrated Product Environment (IPE)—think of it as an IDE for Product Teams.

Just as engineers have VS Code to write, debug, and deploy software, Masterminds provides everything product teams need to research, ideate, design, deliver, and grow a product.

While the IPE interfaces with specialist SaaS tools like Figma (Design), Jira (Program Mgmt), and Amplitude (Metrics) via MCP, all product development intelligence lives inside the platform to be continually used and managed by agents.

The workspace is built on a Context-First Architecture, consisting of three synchronized "Intelligence Engines" that work together to maintain the state of your product.

The Bridge (Top Navigation)​

The "Bridge" is your command center for switching contexts.

  • Initiative Workspaces: Separate environments for entirely different product initiatives. Each initiative has its own team, shared context layer, and database of artifacts.
  • Context Switching: Move between different Sessions (Phases/Workstreams) within the initiative.
    • Session context remains local to the active session.
    • Initiative context now acts as a shared truth layer across sessions in that initiative.
    • Precedence is deliberate: Session > Initiative > System when documents share the same name.

1. Left Panel: The Communication Hub (Directives)​

This is your direct line to the Intelligence Team. This is where you direct the workflow. You define the "What" and "Why"; the agents reason about the "How".

  • Sessions as Phases: Each Session represents a specific Product Development Phase executed by a specific Agent.
  • Flexible Workflows: You can have multiple sessions in one initiative.
    • Example Workflow:
      1. Session A (ODI Innovation Strategy Master): Design an Outcome-Driven Roadmap.
      2. Session B (Solution Discovery Master): Use that roadmap to discover a solution for "Feature X".
      3. Session C (Product Design Master): Design the UI for "Feature X".
      4. Session D (Product Delivery Master): Write the technical specs for "Feature X".
  • Instruction Mode: When you speak here, you are directing an autonomous agent to perform a task, not just asking a question.
  • AI Processing:
    • Thinking: You will see the AIThinkingTerminal while the agent processes your request.
    • Output: The agent delivers "Knowledge Pills" (Deliverables) and text responses.
    • Real-time Streaming: Token-by-token streaming of responses is [#SOON].

2. Center Panel: The Visualizer & Editor​

The Center Panel is where the actual work happens. It is the "Active State" of your product.

  • The Visualizer (Immersive Review): When an agent produces an artifact (e.g., a User Persona, a PRD, or a Code Snippet), it appears here immediately. This allows you to review work without cluttering the chat.
  • The Editor (Advanced Refinement): Click "Edit" to enter the IDE-grade editor.
    • Bi-Directional Sync: Changes you make in the Editor are instantly learned by the agent (committed to memory). You don't need to copy-paste back into the chat.
    • Safer Revision Flow: AI-driven updates are versioned automatically, reducing the risk of losing prior document state by accident.
  • Point of Activation (POA): During onboarding, this panel visualizes your strategic roadmap.

3. Right Panel: Agent Context (The Brain)​

The Right Panel is the Persistent Memory of your project.

  • Deliverables: Every file, document, or snippet generated by the team is stored here.
  • Structure: Deliverables now operate across clear scopes such as Session and Initiative, so you can decide what stays local and what becomes shared truth.
  • External Knowledge: You can upload external documents here to stage context before the next turn.
  • Search: The platform now makes it easier to find sessions and variable content when the initiative becomes large.

The Core Loop: How It Works​

The power of the IPE comes from the interaction between these panels:

  1. Directive (Left): You tell the Customer Discovery Master: "Analyze these interview notes."
  2. Visualizer (Center): The Customer Discovery Master processes the data and generates a Key Insights deliverable, which opens automatically.
  3. Context (Right): The deliverable is saved to the Agent Context.
  4. Editor (Center): You edit the document to add a nuance the Customer Discovery Master missed.
  5. Promotion (Right): If the Customer Discovery Master's insight becomes a reusable truth, drag it to Initiative in the right panel.
  6. Iteration (Left): You tag the Product Design Master: "Use the Customer Discovery Master's insights to draft a solution." The Product Design Master reads the updated shared context and begins work.

This loop—Directive -> Visualization -> Memory -> Refinement—ensures that your product evolves intelligently, with zero context loss.