Filters before full search
Visible filters are cheaper and clearer than a separate search index while content volume is still small.
Phase 4 research
/knowledge/filters-before-searchknowledge.trace("filters-before-search")WorkingSignal
When to use it
Use before adding Fuse, FlexSearch, or external search infrastructure.
Principle
What it protects
It protects the project from adding search infrastructure before the content model is dense enough to justify it. Visible filters keep the system inspectable while tags, languages, kinds, and stacks are still small and editorial.
Reference
How to cite it
Use this decision before introducing Fuse, FlexSearch, external search, or AI search. The current proof is URL-backed filters plus content relation validation.
knowledge.trace("filters-before-search")
Where this idea is used.
knowledge.graph("thin")Most related paths
Product architecture / ShippedStudio Knowledge BaseTurns this knowledge entry into inspectable project evidence.Interaction note / EnglishCommands That Respect AttentionUses this rule as a writing argument in the Interaction note track.Internal referenceBrowse writingConnects this rule to another public route in the studio.Internal referenceBrowse photosConnects this rule to another public route in the studio.BacklinkFilterBarThis page cites the entry because component proof that simple visible filters beat premature search.
Reference links
Backlinks
BacklinkFilterBarComponent proof that simple visible filters beat premature search.This page cites the entry because component proof that simple visible filters beat premature search.BacklinkStudio Knowledge BaseApplied to the public knowledge layer before introducing full-text search.This page cites the entry because applied to the public knowledge layer before introducing full-text search.