ProfessorNovaandClaude Opus 5
784b76baf7
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
53 lines
1.5 KiB
YAML
53 lines
1.5 KiB
YAML
# Catalog blueprint — inert until an admin adds it (docs/authoring-templates.md).
|
|
# The English variant of `stoerung` (same id, locale: en).
|
|
#
|
|
# Written right after something broke, while it is still fresh.
|
|
id: stoerung
|
|
name: "Incident: what happened and what fixed it"
|
|
version: "1.0"
|
|
kind: authoring
|
|
locale: en
|
|
description: >
|
|
After a failure or a fault, record what caused it and how it was resolved.
|
|
|
|
model:
|
|
temperature: 0.35
|
|
min_class_hint: "12b"
|
|
|
|
persona: |
|
|
You are a precise technical editor for incident reports. You write plainly
|
|
and briefly, in complete sentences. Error messages, codes, part numbers
|
|
and readings are quoted verbatim. You separate observation from guess and
|
|
invent no cause. No filler, no emoji.
|
|
|
|
title_template: "Incident on {{date}}"
|
|
|
|
skeleton: |
|
|
## What happened
|
|
|
|
## What caused it
|
|
|
|
## What fixed it
|
|
|
|
## Keeping it from happening again
|
|
|
|
sections:
|
|
- heading: "What happened"
|
|
hint: >
|
|
The symptom: what failed, when, and what it meant for operations.
|
|
Error messages verbatim.
|
|
- heading: "What caused it"
|
|
hint: >
|
|
The cause as far as it is known — anything that is a guess is marked
|
|
as one.
|
|
- heading: "What fixed it"
|
|
hint: >
|
|
The measure that actually resolved it, with the steps in order.
|
|
- heading: "Keeping it from happening again"
|
|
hint: >
|
|
What prevents a repeat: maintenance, a check, a spare part, a change
|
|
to the process. Only what is actually planned.
|
|
|
|
metadata:
|
|
visibility: department
|