How to use workspace search as a second brain

How to use workspace search as a second brain starts with a split most founders miss. One tool jumps you to the right place when you already know the name. Another digs through records when you only remember a fragment. Treat them as two muscles, not one magic box.

In Nautis, the command palette (global search) is the jump tool. Notes search, and each module's own search box, are the dig tools. This guide is product education from Global search and Notes help as of October 2026. It does not claim the palette reads the body of every note yet; the help center is explicit that it does not.

Workspace search as a second brain: jump versus dig

The second-brain habit fails when you type a fuzzy half-memory into the wrong surface. Use this cut:

If you remember Fundraising CRM as a place, jump. If you remember the enterprise pricing objection from March, dig in Notes with a title, tag, or folder you set up on purpose.

What the command palette is for

Press Cmd+K on Mac or Ctrl+K on Windows and Linux from the desktop shell. A centered dialog opens with Type a command or search focused. Results filter as you type. Arrow keys move the highlight; Enter runs the row and closes the palette; Esc cancels.

Results group under section headers such as Navigation (go to a module) and Desktop (interface actions). When you type a short word like deck or lead, read the section label before you hit Enter so you do not open the wrong sibling.

The palette only lists actions your role can use. If a teammate sees more rows, they likely have modules or permissions you do not. Hover highlights a row without arrows. No match shows No commands match that search; shorten the query.

The palette is the same shortcut on the dashboard and deep inside a task board. It is built for navigation and actions. It does not yet search inside individual record bodies (note text, a specific message). For that, open the module and use its search.

Notes as the capture layer of the second brain

Notes is where investor updates, meeting summaries, strategy ideas, and product learnings live as rich text with folders, tags, comments, sharing, and export to PDF or Word. The page splits into a left list (search, status filters for All, Drafts, Published, Archived, pinned-only, folders) and a right editor.

Create with Add Note, title the note before it stays Untitled, and use the slash menu for headings, lists, and tables. Search and folders only help if titles are specific. Prefer Acme pricing objection 2026-03-12 over Meeting notes. Tag by theme (pricing, hiring, raise) so findability survives as the pile grows. Comments belong on contested decisions so the dig finds the debate, not only the conclusion. Export to PDF or Word when a note must leave the workspace; keep the Nautis copy as canonical so later search still hits one source.

Monthly note-creation limits can disable Add Note when hit. That is a signal to archive or merge, not to start a parallel docs pile in chat.

A naming scheme that makes dig search cheap

Second brains rot when every title is a synonym of notes. Pick a small grammar and stick to it for ninety days:

1. Decision: YYYY-MM-DD decision with a one-line outcome
2. Customer: Company, topic, and date
3. Raise: Investor or firm, ask line snapshot, and date
4. Postmortem: Incident, date, and owner

Put the searchable noun first when you will type it later under stress. Store the durable version in Notes, not only in a chat thread the palette cannot read.

One Tuesday that shows the split

Maya needed the SAFE cap she quoted last month and the task board for hiring. She hit Cmd+K, typed cap table, read the Navigation section, and opened Cap Table in two seconds. That was a jump.

She then needed the email wording an angel disliked. She could not remember the angel's name, only discount confusion. Cmd+K returned navigation noise. She opened Notes, filtered the raise folder, searched discount, and opened the dated note. That was a dig. The second brain worked because the note title and folder existed; the palette never pretended to read the body.

Permissions and empty results are signals

Fewer commands than a teammate usually means module access, not a broken shortcut. On mobile layouts, or in a full-screen flow that captures the shortcut, Cmd+K may not open the palette; use the desktop shell. The shortcut is fixed; there is no in-app keybinding editor.

Empty module search usually means the noun never entered a title or tag. Fix the capture habit before blaming the tool. Empty palette search means you are hunting content in a launcher; switch surfaces.

After a no-match palette result, do not invent a new document by reflex. Open the module you believe owns the fact, run its search, and only then create. Reflexive recreation is how a company ends up with three pricing notes and no single answer.

Rituals that keep search honest

Morning: before chat, jump to Chief of Staff with the palette if that is your intake home. Midday: when someone asks where a file lives, try a thirty-second dig in the owning module before recreating the doc. Friday: archive or retitle three vague notes so next week's dig is shorter.

Do not build a second wiki outside Nautis for the same facts. Duplication guarantees the dig finds two answers. If a fact must live in a data room for investors, keep the operator note as a pointer with the dated source, not a conflicting rewrite.

Folders, pins, and status without bureaucracy

Use Draft while a note is still private thinking. Publish when teammates may rely on it. Archive when the decision is done but you may need the trail. Pin the few notes that every Monday still needs (ask line, metric definitions, hiring scorecard). Too many pins recreate the scroll problem search was meant to fix.

Manage folders from the Notes top bar when a theme has more than a handful of notes. Prefer a shallow tree: Raise, Customers, Product, People. Deep nesting hides notes from humans who will not remember the path. Use Refresh on the Notes top bar when a teammate just published something you cannot see yet. Stale lists look like failed search.

What to put in Notes versus what to leave as rows

If the artifact is a person, deal, task, or file pack, keep the system of record in that module and let Notes hold the narrative. Example: Fundraising CRM owns the investor stage; a Note owns the why they passed paragraph. Cap Table owns share counts; a Note owns the explanation you will reuse in the next raise.

When you only paste into Notes, dig search works and operational dashboards go blind. When you only update rows with no Note, the palette can jump to the module but nobody can recover the story. Dual-write the minimum: row for state, Note for rationale, with the same company name spelled the same way in both.

Bad titles that defeat dig search

These patterns look harmless and waste Fridays:

1. Notes from today with no company or topic
2. Call without the counterparty
3. Final without a date or version meaning
4. Joke titles nobody will type under stress
5. Copy-paste chat threads with no title change after Save

Rewrite one bad title the same day you notice it. Future dig search is a tax you pay for every vague Save.

Launcher versus palette when the desk is crowded

Cmd+A or Ctrl+A opens the app launcher when no input field is focused. Use it to switch among open modules. Use Cmd+K or Ctrl+K to run a named jump or action. Mixing them is fine; substituting the launcher for content search is not. If a text field has focus, the launcher shortcut may select all instead; click the canvas background first.

Where Nautis fits without inventing full-text magic

Global search is the command palette for jumping to modules and running actions you are allowed to see. Notes holds the written memory with list search, folders, and tags. Other modules keep their own search boxes for record filters when the answer lives as a row, not a prose note.

Chief of Staff chat can answer from workspace context when you ask a question, but that is not a substitute for naming files so a human dig still works when chat is wrong. Keep the second brain boring: jump when you know the place, dig when you know the fragment, and write titles that future-you would type.

How to use workspace search as a second brain is mostly discipline with two surfaces. The palette moves you. Module search finds what you stored. Store on purpose.