tegwick
044d088109
Activate the workplan and complete T01: add the machine-readable controlled vocabulary canon/standards/repo-classification.allowed.yaml (categories, domains, business_stake, business_mechanics, capability families, guidance), reference it from the standard §12, and add tools/validate_repo_classification.py (stdlib + PyYAML, --self-test PASS). Begin T02: author the-custodian/.repo-classification.yaml (research · infotech · agents), which validates clean. classified_by: agent, pending human review. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
39 lines
1.0 KiB
YAML
39 lines
1.0 KiB
YAML
repo_classification:
|
|
standard: Repo Classification Standard
|
|
version: "1.0"
|
|
classified_at: "2026-06-22"
|
|
classified_by: agent
|
|
|
|
# the-custodian is the governance/continuity substrate: canon, standards,
|
|
# ADRs, charters, memory, and cross-domain coordination scaffolding.
|
|
category: research
|
|
domain: infotech
|
|
secondary_domains:
|
|
- agents
|
|
|
|
capability_tags:
|
|
- governance
|
|
- knowledge
|
|
- coordination
|
|
- policy
|
|
- documentation
|
|
|
|
business_stake:
|
|
- technology
|
|
- operations
|
|
- intelligence
|
|
- execution
|
|
|
|
business_mechanics:
|
|
- intention
|
|
- control
|
|
- coordination
|
|
- adaptation
|
|
|
|
notes: >
|
|
Primary domain is infotech (the intended users are the ecosystem's
|
|
developers and agents); agents is a secondary domain because the repo is
|
|
agent-coordination infrastructure. Classified as research because its core
|
|
output is canon, standards, and decision records rather than a deployable
|
|
product. First-pass agent classification pending human review (CUST-WP-0050 T02).
|