Knowledge browser.

The Knowledge browser is the page at Knowledge Base in the top nav. It lets you read and fork existing knowledge entries. The conceptual model — what a KB entry is, what classifications mean — lives in Knowledge Base.

What you see #

A grid of cards, one per entry. Each card shows:

• Title and one-line subtitle
• Type badge (spec, brownfield, or template)
• Vertical (federal, healthcare, finance, etc.)
• Classification (public, internal, sensitive, cui)
• Stats — features, entities, endpoints, screens captured in the entry
• Reuse count — how many projects have forked from it

Cards you don't have read access to (typically sensitive or cui without a grant) are not shown at all. There's no "you can't see this" placeholder — they're invisible.

Filtering and sorting #

The toolbar has filters by:

• Vertical
• Type (spec / brownfield / template)
• Reuse count (most reused first)

The default view is "most recently added across all verticals."

Forking an entry #

The primary action on every card is Fork as new project. This:

1. Copies the entry's content into a new project as the starting point.
2. Records provenance — the new project knows where it came from, the entry knows it was forked.
3. Carries forward the entry's classification — if you fork a cui entry, the new project inherits cui access controls.

The original is untouched. Editing the forked project does not flow back unless someone explicitly publishes the result as a new entry.

When the browser is empty #

A brand-new workspace has no entries. You can:

• Add a brownfield entry by running the Discovery flow on an existing repo.
• Add a template by archiving a finished project as a reusable starting point (from the project's settings panel).
• Import from another workspace — admins only; involves explicit grants.

There is no global, cross-workspace knowledge base. Every workspace owns its own.