capability_families in repo-classification.allowed.yaml is a fixed list; 'experience' and 'documents' are not in it. Replaced with 'traceability' and 'participation', both in the knowledge_and_evidence family and both accurate: this repository owns the evidence chain and the surface on which a human takes part in a decision. 'decision-support' is in the recommended vocabulary but is still not used, for the statute §8 reason given in the previous commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V3W1dQG7GFFM9d94jFx7iR Assistant: claude-code Assistant-Model: opus Assistant-Process: 1565372@bnt-lap001 Assistant-Session: 16bb2f25-b34c-49ef-8e94-5fec3567a568
29 lines
891 B
YAML
29 lines
891 B
YAML
repo_classification:
|
|
standard: Repo Classification Standard
|
|
version: "1.0"
|
|
classified_at: "2026-09-09"
|
|
classified_by: claude
|
|
category: product
|
|
domain: infotech
|
|
secondary_domains: []
|
|
capability_tags:
|
|
- governance
|
|
- evidence
|
|
- identity
|
|
- traceability
|
|
- participation
|
|
- audit
|
|
business_stake:
|
|
- technology
|
|
- legal
|
|
- operations
|
|
business_mechanics:
|
|
- control
|
|
- operation
|
|
notes: >-
|
|
Presentation and binding surface for decisions — the Decision Memo, and the
|
|
browser-facing approver UI that approval-engine deliberately does not
|
|
contain. Category is product, not project: this is a durable offering with
|
|
emerging product requirements (see workplans/INFD-WP-0001 T03), not a
|
|
bounded cross-repo coordination effort, so the prj- flavor does not apply.
|
|
Not a decision point; access-engine remains the only PDP.
|