tegwick
309bea463e
fix-consistency surfaced that GOAL.md's `repo_flavor: project` was wrong. project-repository-flavor_v0.1.md reserves the prj- flavor for bounded cross-repo coordination efforts and says durable products use INTENT.md and an ordinary category. informed-decision is a durable product, so the C-35 "prj- flavor forbids shipping both INTENT.md and GOAL.md" contradiction was self-inflicted rather than a real conflict. - .repo-classification.yaml: category product, domain infotech. - GOAL.md: drop repo_flavor/project_status, add a flavor note explaining that GOAL.md is retained as the stage statement alongside a stable INTENT.md. - SCOPE.md: honestly empty — states that nothing is implemented and that INFD-WP-0001-T06 rewrites it after the gate-house ruling and the specs. - AGENTS.md: shared State Hub / session / workplan boilerplate, plus the hard rules for this repository — never decide, never own approval state, never invent identity, never let awareness enter view_hash, never let an agent bind, never fork the schema, fail closed. - INFD-WP-0001: T01 records both corrections; T06 now rewrites SCOPE.md. 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
28 lines
873 B
YAML
28 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.
|