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
This commit is contained in:
parent
5985e5ddbd
commit
c42cb88d31
1 changed files with 22 additions and 0 deletions
22
.repo-classification.yaml
Normal file
22
.repo-classification.yaml
Normal file
|
|
@ -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).'
|
||||
Loading…
Add table
Add a link
Reference in a new issue