pattern-transfer

Cross-domain pattern transfer works by evaluating structural invariants and contraindications from a pattern catalog to propose governance-aware adaptations for a target domain. It computes structural matches using formal pattern-card frontmatter to ensure responsible reuse.

To transfer a pattern safely, identify a candidate in the pattern catalog, evaluate its transfer viability against structural invariants, pass the strict risk gate, and draft an audit-ready transfer proposal with post-transfer validation to prevent premature deployment.

Use governance checks for domain adaptation when moving best-practice solutions between different contexts to enforce a strict risk gate. This prevents premature deployment by validating structural invariants and contraindications before applying the transferred pattern.

Yes, pattern transfer operates on the pattern catalog stored under contexts/memory/patterns. Each pattern must use a formal frontmatter structure to compute structural matches, assess transfer viability, and generate audit-ready pattern-card updates for traceability.

Invariant-based pattern transfer enforces a strict risk gate and post-transfer validation, meaning transfers with high risk levels or unresolved contraindications will be blocked. It is limited to patterns with formal frontmatter and cannot bypass governance checks for premature deployment.