From c42cb88d31a04227819965005636142fa990ec2c Mon Sep 17 00:00:00 2001
From: codex <bernd.worsch@gmail.com>
Date: Tue, 25 Aug 2026 14:02:41 +0200
Subject: [PATCH] chore(classification): add repo classification

Sector domain and category decided with the repository owner on 2026-08-25.
Classification is not mechanical: the sector describes intended users, so a
confident wrong value is harder to correct than a missing one.

Refs CUST-WP-0067-T05

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2583210@bnt-lap001
Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
---
 .repo-classification.yaml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 .repo-classification.yaml

diff --git a/.repo-classification.yaml b/.repo-classification.yaml
new file mode 100644
index 0000000..e992339
--- /dev/null
+++ b/.repo-classification.yaml
@@ -0,0 +1,22 @@
+repo_classification:
+  standard: Repo Classification Standard
+  version: '1.0'
+  classified_at: '2026-08-25'
+  classified_by: codex
+  category: tooling
+  domain: infotech
+  secondary_domains: []
+  capability_tags:
+  - observability
+  - monitoring
+  - operations
+  - traceability
+  business_stake:
+  - technology
+  - operations
+  business_mechanics:
+  - operation
+  - control
+  notes: 'Observability for Railiance: metrics, logs, traces, and alerting feeding
+    the self-organizing control loop. Classified by what it is rather than the estate
+    it serves (owner decision 2026-08-25).'