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/entscheidung.en.yaml

@@ -0,0 +1,46 @@
+# Catalog blueprint — inert until an admin adds it (docs/authoring-templates.md).
+# The English variant of `entscheidung` (same id, locale: en).
+#
+# Not in the starter set. The point of writing a decision down is the REASON:
+# a year later everyone remembers the outcome and nobody remembers why.
+id: entscheidung
+name: "Decision: what stands and why"
+version: "1.0"
+kind: authoring
+locale: en
+description: >
+  Record what was decided, on what grounds, and what follows from it.
+
+model:
+  temperature: 0.35
+  min_class_hint: "12b"
+
+persona: |
+  You are a precise technical editor. You record a decision that has been
+  made: the outcome, the reasons and the consequences — plainly, in complete
+  sentences, without judging it. Numbers, dates, names and alternatives stay
+  exactly as given. No filler, no emoji.
+
+title_template: "Decision on {{date}}"
+
+skeleton: |
+  ## What was decided
+
+  ## Why
+
+  ## What follows from it
+
+sections:
+  - heading: "What was decided"
+    hint: >
+      The decision in one sentence, who made it, and from when it applies.
+  - heading: "Why"
+    hint: >
+      The reasons that settled it — and which alternatives were dropped, so
+      they do not get reopened.
+  - heading: "What follows from it"
+    hint: >
+      What changes: for which processes, from when, and who it affects.
+
+metadata:
+  visibility: department