feat: participation and RACI labels, written on the project page (#118)

Files changed:
- CHANGES.md
- VERSION
- instructions/gtd-weekly-review/SKILL.md
- instructions/link-taxonomy.md
- kb/entities/COLLECTION.md
- kb/gtd/COLLECTION.md
- types/project.md

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

kb/entities/COLLECTION.md

@@ -1,7 +1,7 @@
 ---
 profile: entities
 outbound:
-  entities: [depends-on, required-by, runs-on, hosts, uses, produces, consumes, maintains, owns, authored, alternative-to, implements, part-of, composition, supersedes, derived-from, adapted-from, see-also]
+  entities: [depends-on, required-by, runs-on, hosts, uses, produces, consumes, maintains, owns, owned-by, authored, involves, alternative-to, implements, part-of, composition, supersedes, derived-from, adapted-from, see-also]
   concepts: [implements, exemplifies, rests-on, applies-when, operates-on, invokes, authored, alternative-to, see-also]
   sources: [evidenced-by, defined-in, see-also]
   comparisons: [compares-with, see-also]
@@ -66,6 +66,13 @@ mirrored clique grows fastest. `derived-from` and `adapted-from` are here for th
 re-implementation - one tool worked up out of another - which is a lineage claim the operational
 labels cannot make.
 
+`involves` and `owned-by` are the participation labels, and they run the other way from
+`authored`/`owns`/`maintains`: written on the codebase or system, pointing at the person or
+organization - `[Codebase] involves [Person]`. `involves` is the contributor who neither answers
+for the thing nor keeps it running; take `maintains` or `owns` from the person's side when one of
+those is true instead. `owned-by` is `owns` read from the thing's side - write whichever page a
+reader would ask the question on, not both by reflex.
+
 Adding a label here is a deliberate contract change, not a way around a refusal.
 
 ## Outbound linking

kb/gtd/COLLECTION.md

@@ -1,7 +1,7 @@
 ---
 profile: none
 outbound:
-  entities: [see-also]
+  entities: [involves, owned-by, see-also]
   concepts: [see-also]
   sources: [see-also]
   gtd: [see-also]
@@ -53,15 +53,28 @@ their own. The initial three values are this instance's own starting vocabulary
 - **`## Beteiligte` carries mentions, not links (D28).** One to two lines per person, in prose,
   with no `[[wikilink]]` and no page of their own. This is a deliberate, named exception to
   `kb/CONTRACT.md` § "Every page should" - a project page with unlinked people in its
-  `## Beteiligte` section is conforming, not incomplete. A person earns their own page, and the
-  mention becomes an edge, only once they matter for the knowledge independent of this one
-  initiative.
+  `## Beteiligte` section is conforming, not incomplete. A person earns their own page only once
+  they matter for the knowledge independent of this one initiative. From then on the exception
+  no longer covers them: the mention stays, gains a `[[wikilink]]`, and the project page - this
+  one, not the person's - carries the edge (see Authorised labels).
 
 ## Authorised labels
 
-Only `see-also` is authorised in every direction for now. The vocabulary a participation edge
-(person -> project) would use is a deliberate later addition, not an oversight - adding it is a
-collection-contract change made when that label exists, not a way around a refusal.
+Participation is written on the project page, pointing at the person or organization:
+`[Projekt] involves [Person]`. The page is where "who is involved?" gets asked, and a page's own
+links block shows only the edges it carries. Two labels are authorised for it, drawn from
+[instructions/link-taxonomy.md](../../instructions/link-taxonomy.md) § Operational:
+
+- `involves` - takes part, role not stated. The default for a household initiative.
+- `owned-by` - the one who answers for the initiative's existence and decisions; the inverse of
+  `owns`, which a person page may still carry independently.
+
+The catalogue also holds the RACI labels `staffed-by`, `consults` and `informs`. This instance
+does not authorise them - its initiatives are too small for the distinction to earn its upkeep -
+but an instance tracking client work adds them here, a deliberate contract change like any other.
+
+Every other direction is `see-also` only for now. Adding a label is a collection-contract change,
+not a way around a refusal.
 
 ## Outbound linking