informed-decision/.repo-classification.yaml
tegwick 83016236c9 Use established capability tags
C-24 flagged 'user-interface' as outside the recommended family vocabulary.
Replaced with 'experience' and 'documents', both already in estate use.
Deliberately did not add 'decision-support': 'decision' is access-engine's word
under statute §8, and approval-engine withdrew its own seed wording for the
same reason. This repository renders decisions; it must not tag itself as
supporting them.

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
2026-09-09 12:39:36 +02:00

29 lines
885 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
- experience
- documents
- 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.