Skip to content

TECHNIQUE_KIND_GUIDE.md

Latest commit

 

History

History
64 lines (45 loc) · 3.49 KB

TECHNIQUE_KIND_GUIDE.md

File metadata and controls

64 lines (45 loc) · 3.49 KB
Raw

Technique Kind Guide

This is the living doctrine for the kind axis in aoa-techniques.

Use it when you are writing, reviewing, or selecting a technique and need the bounded second cut after domain.

See also:

Core Doctrine

  • domain stays the ownership and first-routing axis.
  • kind is the bounded second selector axis inside that owner layer.
  • kind names the atomic move shape; it is not the family, substrate, capability class, or risk posture.
  • Each technique chooses exactly one primary kind.
  • Use tags for extra nuance instead of widening kind.
  • Keep family scout-only and non-authoritative in this wave.

How To Choose

Pick the narrowest honest kind that helps a selector understand default use.

If two kinds feel plausible, use the registry tie-break rules:

  • workflow vs guardrail: choose workflow for stepwise doing, guardrail for stopping, narrowing, or approving.
  • validation vs assessment: choose validation for proof or integrity evidence, assessment for classification or diagnosis.
  • artifact vs lift: choose artifact for the primary durable shape, lift for a weaker derived surface from stronger source material.
  • composition vs distribution: choose composition when parts become one result, distribution when one source fans out to many targets.
  • handoff vs workflow: choose handoff when continuation across a seam is the main contract, workflow when the work loop itself is the main contract.

ingest stays reserved for raw external inputs that are being normalized into reviewable intermediates.

Review Rules

  • Reviewers should check that the selected kind is singular and narrow.
  • Reviewers should prefer registry-backed tie-breaks over local intuition when the choice is close.
  • Reviewers should not use kind as a status, score, or promotion signal.
  • Reviewers should send cluster questions to family only as scout notes, not as frontmatter truth.

Current Source Files

The current canonical sources for this axis are:

  • config/technique_kind_registry.yaml
  • mechanics/distillation/parts/technique-reform-ingress/data/technique_kind_overlay.yaml
  • mechanics/distillation/parts/technique-reform-ingress/reports/technique_kind_counts.md

The living corpus still belongs in the technique bundles and generated catalog. This guide only defines how to choose and review the axis.

Historical Baseline

The first kind-axis pass established domain as the ownership and first-routing axis, with kind as the narrow second selector. It intentionally kept family optional and scout-only, left tags freeform, and bounded the adoption pass so the corpus could gain kind without turning the axis into a new policy layer.