Power Patterns
Power patterns are reusable building blocks — not one-off examples. Each pattern encapsulates a technique that appears repeatedly across production rules: accessing shared parameters safely, building lookup indexes, and combining type and instance data.
Learn these patterns once. Reuse them everywhere.
What you will learn
- How to access shared parameters by GUID in a safe, reusable way
- How to upgrade basic parameter access with model-aware validation
- How to combine symbol and instance data into a single enriched output object
Pages in this section
Shared Parameter Access
A reusable helper function for reading shared parameters by logical name. Introduces the GUID map pattern and safe parameter resolution.
Model-Aware Shared Parameter Access
An improved version that uses Parameter objects from the model as the authoritative source — detecting missing parameter bindings and returning real metadata.
Symbol–Instance Data Enrichment
How to build a symbol lookup index and use it to enrich instance output with type-level data. The canonical pattern for rules that need both symbol and instance fields.
Prerequisites
You should already understand:
- Shared parameters and GUIDs — see Identity vs Value
- The two-step filter pattern — see Two-Step Filtering
- Conditional output fields — see Conditional Output Fields
Power patterns should not be modified lightly. If you change them, understand why, document what changed, and verify the output shape. These patterns exist to reduce risk, not increase cleverness.