Search the Workspace

One search across everything

The command center opens with ( on Windows/Linux). It searches the entire workspace at once — platforms, programs, assets, every component type, and playbooks — and every result opens directly.

Type plain text to search names, or add filters to slice the vault. Filters combine with AND: type:playbook difficulty:high means high-difficulty playbooks only. Negation works on tags and presence: !tag:wip, !has:quirk.

Finding the thing in front of you

• has:functionality:"File Upload" — every entity connected to file uploads.
• type:asset priority:critical — the assets that matter most.
• version:>=14 — technology links at or above a version.
• created:7d / updated:30d — what changed recently.

Autocomplete (press ) completes filter names and values, and active filters appear as chips you can clear individually. The complete grammar lives in the search syntax reference.

Hunting horizontally

The command center is also the fastest way to answer cross-workspace questions — the ones a single asset page can never answer:

• "Where is this technology?" — has:technology:Caddy across every program at once.
• "What did we tag as needing review?" — !tag:reviewed or a status filter, depending on what you track.
• "What does the library connect to?" — has:gadget:"GraphQL endpoint" to see every asset and playbook that touches it.

This is the moment the vault pays you back: knowledge that was entered engagement by engagement becomes queryable across all of them.

Practical habits

• Filter, then read. Text alone floods; one or two filters turn the vault into an answer.
• Quote multi-word values — has:func:"File Upload".
• Use the chips to iterate. Build a query in the box, then refine by clearing the one filter that is too narrow.
• Everything is a result. If it exists in the vault — an asset, a component, a playbook, a platform — search returns it.

What's next

• Search syntax reference — every filter, alias, and operator.
• Map an asset — keep the vault worth searching.