source_type ist Instanzsache: Profilkatalog, Setup-Frage, evolve-subtypes-Instruction (schliesst #68)
CI / verify (push) Successful in 52s
Release / release (push) Successful in 34s

Files changed:
- CHANGES.md
- VERSION
- instructions/evolve-subtypes.md
- instructions/kb-profiles.md
- instructions/setup-instance.md
- kb/sources/COLLECTION.md
This commit is contained in:
2026-09-09 07:50:18 +02:00
parent 46dfee0ea9
commit 6b300aa782
6 changed files with 211 additions and 3 deletions
+24
View File
@@ -152,6 +152,30 @@ against.
Not optional in the way the others are. An instance may rewrite its authoring rules and may not
rename or drop it.
**`source_type` is a palette too, and the part most likely to be wrong for another domain -
adapt its value list first**, the same way `entities`' area list is called out above. This
repo's own list (`transcript, analysis, article, document, notes, tracker, unclassified`)
describes *what a private-projects instance ingests*; it says nothing about what a source is in
a different domain. Two worked lists, to show how little the values carry over:
| Instance | Plausible `source_type` values |
|---|---|
| Handball club and federation | `satzung` (bylaws), `protokoll` (minutes), `korrespondenz`, `spielbericht` (match report), `verbandsmitteilung` |
| Tabletop game master | `regelwerk` (rulebook), `abenteuermodul` (module), `sessionlog`, `handout`, `weltenbau` (worldbuilding) |
Adopting one means copying the value list into `types/source.schema.yaml`'s enum and giving each
value a `layout:` line in `types/source.md` - the same "copy the text in, do not point at this
page" rule as every other profile here. Keep the visible catch-all value (`unclassified` above)
in whatever list is adopted: a subtype field without one silently reintroduces the old
`default:`-driven collection point that Gitea #66 removed the moment nobody names an edge case.
Growing the list later, or draining the catch-all, is
[evolve-subtypes.md](evolve-subtypes.md).
**Not up for choice: `fidelity` and `authority`.** Unlike `source_type`, these two capture
fields are stack vocabulary - `types/source.md`'s `capture_fields:` - because they held the same
few values across every domain this catalogue tried, where `source_type` did not. An instance
adapts the *value list* above; it does not touch `fidelity`'s or `authority`'s enums.
### `comparisons`
Structured head-to-head evaluations of two or more things that already have pages.