chore(classification): add repo classification
Sector 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-0068 Assistant: claude-code Assistant-Model: opus Assistant-Process: 2583210@bnt-lap001 Assistant-Session: f2bff2d5-e9b2-4338-92ca-10282a927006
This commit is contained in:
parent
5a010a9357
commit
da0da8b4e4
1 changed files with 21 additions and 0 deletions
21
.repo-classification.yaml
Normal file
21
.repo-classification.yaml
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
repo_classification:
|
||||
standard: Repo Classification Standard
|
||||
version: '1.0'
|
||||
classified_at: '2026-08-25'
|
||||
classified_by: codex
|
||||
category: tooling
|
||||
domain: agents
|
||||
secondary_domains: []
|
||||
capability_tags:
|
||||
- observability
|
||||
- orchestration
|
||||
- operations
|
||||
- integration
|
||||
business_stake:
|
||||
- technology
|
||||
- operations
|
||||
- automation
|
||||
business_mechanics:
|
||||
- control
|
||||
- operation
|
||||
notes: Mission control for Kubernetes hosts, exposed to LLM agents through MCP.
|
||||
Loading…
Add table
Add a link
Reference in a new issue