Research an external subject using web search, synthesize findings into a structured Basic Memory entity. Use when asked to research a company, person, technology, or topic — or when a bare name or URL is provided that implies a research request.

Memory Research Research an external subject, synthesize what you find, and create a structured Basic Memory entity — with the user's approval. Project scope If the project is unknown, discover it with bm project(command="list") . Pass a nonempty project on every note, folder, context and schema call, even with one project or a qualified memory:// URL. Use the chosen project's name, workspace/project , or external ID; <project below is a placeholder for it. Recent activity also requires project . Search accepts project for one project, projects for selected projects, or all projects=True explicitly. Discovery and bundled manuals need no project. Keep the same scope when following returned paths, paginating, or recovering from a refusal. Workflow Step 1: Web Research Basic Memory does not include a web search tool. If this host already has one, use it. If it does not, the user can add any web search tool or MCP server, for example [Parallel Search MCP](https://docs.parallel.ai/integrations/mcp/search mcp). Search queries go to that provider, so keep private note content out of them. Still ask before saving a note. Search for current information across multiple sources. Aim for 3 5 searches to build a well rounded picture: What to gather by entity type: Entity Type Key Information Organization What they do, products/services, stage (startup/growth/public), funding, leadership, headquarters, employee count, notable partnerships or contracts Person Current role, organization, background, expertise, notable work, public presence Technology What it does, who maintains it, maturity, ecosystem, alternatives, adoption Topic/Domain Definition, current state, key players, trends, relevance to user's context Step 2: Check Existing Knowledge Before proposing a new entity, search Basic Memory: Try name variations — full name, abbreviation, acronym, domain name. If the entity already exists: Report what you found in Basic Memory alongside your web research Offer to update the existing note with new information Use bm edit to append new observations or update outdated ones If the entity doesn't exist, proceed to evaluation. Step 3: Evaluate and Summarize Present your findings in a structured summary. Include all relevant information organized by section: Evaluation Guidelines Use hedging language. Web research is a snapshot, not ground truth: "Appears to be", "Based on public information", "Estimated" "As of [date]", "According to [source]" Put the as of date on the observation, so a later search by date finds it (see memory notes ): [stage] @valid:2026 10 Series B, about 200 employees (public information) Never state funding amounts, employee counts, or revenue as exact unless citing a primary source Don't fabricate. If information isn't available, say so: "Leadership information not publicly available" "Funding details not disclosed" Let the user define relevance. Don't impose a fixed evaluation framework. Instead, highlight facts and let the user draw conclusions. If the user has a specific evaluation rubric (strategic fit, buy/partner/compete, etc.), they'll tell you — apply it when asked. Step 4: Propose Entity Creation After presenting the summary, ask for approval: If the user provided context with their request ("saw them at the conference"), include that context in the proposed entity. Step 5: Create the Entity After approval, create a structured note. Adapt the template to the entity type: Organization Person Technology Adapt these templates freely. The key elements are: note type/tags parameters, an overview, structured details, observations with categories, and relations. If bm write reports similar existing notes, check whether one of them is this entity before keeping the new note; merge or link instead of duplicating. Step 6: Store Source Context If the user provided context with their request, capture it in the entity: This context is often the most valuable part — it's the user's relationship to the entity, which web research can't provide. Guidelines Always web search. Don't rely on training data alone. Research should reflect current, verifiable information. Search Basic Memory first. Check for existing entities before creating new ones. Update rather than duplicate. Hedge uncertain information. Use qualifiers for estimates, unverified claims, and inferred details. Store source URLs. Include the URLs you consulted, either in observations or a Sources section. This enables the user to verify and dig deeper. Get approval before creating. Present your findings and let the user decide whether to create the entity and what to include. Capture user context. If the user told you why they're researching (met at a conference, evaluating as a vendor, etc.), that context belongs in the entity. Don't over research. 3 5 web searches is usually enough. The goal is a useful knowledge graph entry, not an exhaustive report. Link to existing knowledge. Relate the new entity to things already in the knowledge graph. Connections compound value.

memory-research