> Trending topics, emerging themes and a page for every topic, drawn from what your publication has published: Papyrus's real knowledge components with sample data.

Canonical: https://p.apyr.us/cookbook/knowledge-base/

::band{id="top" size="hero" eyebrow="Cookbook · Recipe"}
# A living knowledge base.

Show readers what your publication knows: what's being talked about more this month, which themes are emerging, and a page for every topic you cover. Everything below is Papyrus's real component, drawn from The Wet Weave's sample data. Each one is a single line in a page. [Beta]

::band{id="trending" tone="muted" eyebrow="Trending" columns="top"}
## What's moving this month.

A strip of the topics mentioned more than usual, each with its trend. The change is always printed as numbers beside the mark, never shown by colour alone.

```
::include{kind="block" name="knowledge-trending-strip" limit=5}
```

::column{panel="card"}
::include{kind="block" name="knowledge-trending-strip" limit=5}

::band{id="ranked" eyebrow="Ranked" columns="top"}
## A ranked list readers can filter.

The same trends as a ranked list with item counts. Readers filter it by kind (techniques, materials, clubs, gear) without any script.

```
::include{kind="block" name="knowledge-trending-list" limit=6}
```

::column{panel="card"}
::include{kind="block" name="knowledge-trending-list" limit=6}

::band{id="themes" tone="muted" eyebrow="Themes" columns="top"}
## Themes as they emerge.

Each week Papyrus finds themes across what you've published and marks them New, Growing or Cooling, with who accepted each one.

```
::include{kind="block" name="knowledge-clusters" limit=4 terms=4}
```

::column{panel="card"}
::include{kind="block" name="knowledge-clusters" limit=4 terms=4}

::band{id="concept" eyebrow="Concept of the week" columns="top"}
## One concept a week.

The topic that came up most in the last four weeks, with a short description and who wrote or reviewed it.

```
::include{kind="block" name="knowledge-concept-of-the-week"}
```

::column{panel="card"}
::include{kind="block" name="knowledge-concept-of-the-week"}

::band{id="beat" tone="muted" eyebrow="Beats" columns="top"}
## A beat's pulse.

For each beat your publication covers: how much you've published lately, and the topics that come up in it most.

```
::include{kind="block" name="knowledge-beat" key="techniques" part="trend"}
::include{kind="block" name="knowledge-beat" key="techniques" part="entities"}
```

::column{panel="card"}
::include{kind="block" name="knowledge-beat" key="techniques" part="trend"}
::include{kind="block" name="knowledge-beat" key="techniques" part="entities"}

::band{id="topic" eyebrow="Topic pages" columns="top"}
## A page for every topic.

Each topic you've accepted gets its own page: a weekly chart (with your own annotations), the topics it's mentioned with, the stories that mention it, and who accepted it and reviewed its description.

```
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="trend" annotate="2026-10-02" annotateLabel="Weaving night starts"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="neighbourhood"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="related"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="provenance"}
```

::column{panel="card"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="trend" annotate="2026-10-02" annotateLabel="Weaving night starts"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="neighbourhood"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="related"}
::include{kind="block" name="knowledge-entity" key="hover-weaving" part="provenance"}

::band{id="process" tone="card" eyebrow="The editorial process" columns="top"}
## How it stays honest.

Nothing here is written by a language model when a reader loads the page. Once a week, Papyrus analyses what you've published and proposes topics and themes. An editor accepts them, or an AI reviewer does and every page says so. Descriptions show who wrote and who reviewed them, and readers can suggest an edit to any topic page.

1. **The weekly run.** Your published stories are grouped into themes and counted week by week, so this week can be compared with the last.
2. **Proposals.** New topics and themes start as proposals, never published until they're accepted.
3. **Review.** An editor, or an AI reviewer you choose, accepts or rejects each one. The stamp on every page says which.
4. **Readers.** Topic pages are read-only, with a suggest-an-edit form that goes to your editors.

[How the knowledge base works](/public-knowledge-base.html). See it running on [Shipped](https://shipped.anth.us/), our own publication about AI models.
