Pablan, as it stands

Self-hosted knowledge management for SMEs: a split-screen Markdown editor
whose sections an LLM refines while you write, and RAG question answering
over the documents that result. FastAPI + Postgres/pgvector on the back,
SvelteKit on the front, everything OpenAI-compatible and self-hostable.

Squashed into a single commit; the development history stays local.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CA43ZJda8Rbp2hKXNy8f6b

templates/prozess.en.yaml

@@ -0,0 +1,54 @@
+# Catalog blueprint — inert until an admin adds it (docs/authoring-templates.md).
+# The English variant of `prozess` (same id, locale: en).
+#
+# The most common thing anyone writes down: how something is done here. The
+# headings are the questions a colleague actually asks.
+id: prozess
+name: "Process: how we do this"
+version: "1.0"
+kind: authoring
+locale: en
+description: >
+  A recurring process, step by step — written so somebody else gets through
+  it alone.
+
+model:
+  temperature: 0.4
+  min_class_hint: "12b"
+
+persona: |
+  You are a precise technical editor for work instructions. You write
+  plainly, in complete sentences, and turn a sequence into a numbered list.
+  Numbers, deadlines, system names and responsibilities stay exactly as
+  given, and you invent none. No filler, no emoji.
+
+title_template: "New process"
+
+skeleton: |
+  ## When this applies
+
+  ## Step by step
+
+  ## When it goes wrong
+
+  ## Who owns it
+
+sections:
+  - heading: "When this applies"
+    hint: >
+      The trigger: the situation this process covers, and where it does not
+      apply.
+  - heading: "Step by step"
+    hint: >
+      The steps in order, each one an action — with the systems, forms and
+      deadlines that belong to them.
+  - heading: "When it goes wrong"
+    hint: >
+      The special cases and the places this reliably snags, and what to do
+      then.
+  - heading: "Who owns it"
+    hint: >
+      Who is responsible for the process and who to ask about it.
+
+metadata:
+  visibility: department