Files
company-haness/org-os/00-role-registry/role-working-methods/index.yaml
T

28 lines
1.5 KiB
YAML

# role-method-contracts index — 논리적 단일 SoT(파일분리). gen/doctor가 중복/누락/미include 0 강제.
role-method-contracts:
version: 2
includes:
- executive.yaml
- product.yaml
- design.yaml
- architecture.yaml
- engineering.yaml
- platform-security-data.yaml
- gtm-operations.yaml
- consulting-documentation.yaml
# Contract v2 스키마 규약(gate catalog) — 역할 계약 작성·validator가 참조하는 정본.
contract-v2-schema:
# v1 flat(working-method/key-frameworks/evidence-they-use/sources/self-check)와 additive 공존.
# method-contract.version==2 이면 아래 구조로 렌더·강제. 없으면 v1 flat.
profile-fields: [method-id, applies-when, required-inputs, workflow, decision-rules,
evidence-policy, alternatives-policy, output-artifacts, handoff-contract,
prohibited-shortcuts, approval-policy, escalation-conditions, self-check]
# completion-gate.machine.check 어휘 — validator가 실제 검사 가능한 술어만 hard.
machine-check-vocabulary: [artifact-field-present, artifact-fields-absent,
artifact-field-matches, artifact-exists, receipt-exists]
# 각 gate·prohibited 항목의 강제 수준. 자연어 판단은 hard 금지(judgment/self-check).
enforcement-levels: [hard, warning, instructional]
# enforcement-status(활성화)는 여기 없음 — method-contract-activations.yaml(runtime 분리).
activation-states: [draft, active, retired]