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
9c791ff8c0
commit
4a422ed195
1 changed files with 20 additions and 0 deletions
20
.repo-classification.yaml
Normal file
20
.repo-classification.yaml
Normal file
|
|
@ -0,0 +1,20 @@
|
||||||
|
repo_classification:
|
||||||
|
standard: Repo Classification Standard
|
||||||
|
version: '1.0'
|
||||||
|
classified_at: '2026-08-25'
|
||||||
|
classified_by: codex
|
||||||
|
category: research
|
||||||
|
domain: government
|
||||||
|
secondary_domains: []
|
||||||
|
capability_tags:
|
||||||
|
- simulation
|
||||||
|
- governance
|
||||||
|
- analytics
|
||||||
|
business_stake:
|
||||||
|
- intelligence
|
||||||
|
- finance
|
||||||
|
business_mechanics:
|
||||||
|
- intention
|
||||||
|
- adaptation
|
||||||
|
notes: Agent simulation laboratory for governance and resource-allocation mechanism
|
||||||
|
design; scenario sweeps and KPI comparison before real-world deployment.
|
||||||
Loading…
Add table
Add a link
Reference in a new issue