---
id: ch4-replicate-region
type: spine
title: "Replicate Klatovsko in your region"
readingTime: 2
standalone: true
core: false
teaser: "Ten local questions, the layers that answer them, and a draft shared with the consortium: a knowledge base people can check and maintain."
voice: universal
parent: null
diagram: null
recallQ: "What is the workflow for replicating the Klatovsko knowledge base in another pilot region?"
recallA: "Pick ten questions locals actually ask, define places and dates, map each to European and national layers with their provenance fields, draft evidence-linked blocks in the author studio, share them with group code polirural, and let editorial review lift the best into the book; then assign maintenance."
highlights:
  - "Start from questions people ask, not from a data catalogue"
  - "European layers exist for every pilot; national layers add the operational detail"
  - "Record the D4.2 priority fields: source, provider, dates, update status, licence, access, limits, quality"
  - "Humans decide what is published; agents draft and check"
status: accepted
concept: replicate-local-kb
conceptTitle: "Replicating the local knowledge base"
parents: local-geoai-kb|klatovsko-open-data
lang: en
lens: generic
depth: standard
formalism: none
visuality: text-first
lengthBand: standard
genre: worked-example
state: edited
carriers: prose
---

The Klatovsko pattern needs a defined territory, a small editorial team and questions that matter locally. Identical datasets are not required.

- [ ] **Pick ten questions locals actually ask.** "Which settlements have a mapped walking route to services?" beats "Describe regional sustainability."
- [ ] **Define places and dates.** Record the boundary, administrative identifiers and the period each question concerns.
- [ ] **Map each question to layers.** Every pilot has the European layers D4.2 integrates: OpenStreetMap, Eurostat and GISCO units and statistics, WorldClim and ERA5 climate, Open Land Use. National layers add the operational detail: LPIS, cadastre, address registers, the national statistics office.
- [ ] **Record provenance.** For each layer, note the D4.2 priority fields: source, provider, temporal coverage, update status, licence, access level, known limitations and quality status. Write "unknown" or "not provided" instead of leaving a gap.
- [ ] **Draft blocks in the author studio** (✍️ on any block): one question, a short explanation, linked evidence, scope, limits and a named human steward.
- [ ] **Share with group code `polirural`.** Colleagues test the explanation and add tellings in the gallery. Agents can submit drafts through `POST /api/drafts`.
- [ ] **Ask for editorial review.** Sharing is not acceptance; editors lift the best drafts into the book.
- [ ] **Plan maintenance.** Name who corrects what, and flag blocks whose evidence has aged.

**Humans decide, agents help.** Agents can find candidate sources, suggest metadata, structure a draft and flag unsupported claims. A generated citation must be opened and checked, and a spatial calculation needs an inspectable method. The pilots' policy brief puts this role into an institution, the **digital steward** who mediates between developers and local users.

**Sources:**
- D4.2 PoliRuralPlus platform Beta, §4.1 Integrated data sources and pilot data flows; §4.4 Provenance, data quality and reuse conditions — [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D7.3 Policy Brief No. 1, Annex 10, Strategic recommendation 5: Digital Steward Training Programme — [PDF](https://www.poliruralplus.eu/docs/349/D7.3_Policy_Brief_No.1.pdf)
- This book's contribution brief: `/AGENTS.md`