A shared knowledge base for ReFi Barcelona.

One store

423 typed objects (7 schemas) · 369 in review · 0 published

• resource 133
• signal 86
• encyclopedia-entry 82
• public-use-boundary 54
• claim-evidence 34
• concept-lineage 27
• source-system 7

The typed store lives in this repo (kb/, one markdown file per object) beside the CRM registry, which remains in refi-bcn-os (data/crm.yaml) with the org registries — one band of the common layer, not the whole of it. Local files hold field authority over the Notion mirror — the Flows band below states exactly how far that goes — and /system carries the authority table.

The containers themselves are attributed 416 of those objects; the remaining 7 are source cards — a card describes a container rather than belonging to one.

Common ontology — being defined

Each container keeps its own ontology: toolkit schemas over the old knowledge base, CRM rules over the registry, its own model over the map. The shared layer between them is deliberately gradual — it was tabled at the 260811 sync rather than settled, with Giulio leading and the OS↔Notion mapping doc as the starting point.

Nothing here claims one vocabulary yet. The ontology row of the matrix above states what each container actually uses today.

Publication gate

One gate, and it fails closed: only reviewed, in-scope objects publish, and they publish cut as curated collections — definitions over the store, never copies, recomputed at every build.

• Regeneration in Catalunya — 15 members · 0 publishable — entries appear as review promotes them

/collections renders whatever the reviewed definitions file holds.

Flows

• notion:sync gives local YAML field authority — Notion never overwrites a field.
• Existence syncs both ways: local records are created in Notion, and Notion-created rows come down only under an explicit --import.
• The CRM build feed refreshes every 6 hours.
• Git carries history and review.