29 lines
873 B
YAML
29 lines
873 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
|
||
|
|
- user-interface
|
||
|
|
- 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.
|