# Map a reviewed shared definition into a product

Map every required input to a selected native revision and inspect the complete retained configuration before saving.

Source: https://help.smartfact.ai/manuals/automation/definition-mappings

Review edition: 25 October 2026

Roles: author, reviewer

Mapping makes a specific reviewed shared definition usable in a compatible product's native configuration. It binds exact versions and explicit inputs. It does not give one product unrestricted access to another's operational facts or remove the native release workflow.

## Choose the exact source and definition

From the requirement, choose Map a reviewed shared classification. Select the product, site, native subject and available mapping slot. Obtain the protected current source view and inspect its revision and context.

Choose Definition reference and exact reviewed revision. Check that the definition's intended meaning and outputs match the native slot. A later draft with a familiar name is not interchangeable with the selected reviewed version.

## Map every input deliberately

Use Map every input to supply the allowed native values. Preserve types, units and exact identity codes. Missing information must remain explicit; do not substitute another field merely because its current value resembles the expected input.

Prepare and review the complete mapping. Inspect source identities, definition hash, all input choices and the product's proposed retained configuration. Where the workflow supports retaining it for a plan, keep the exact reviewed mapping and source context with that step.

## Save into the native lifecycle

Use the explicit save or preparation action for the checked mapping. The native product rechecks current source revision, authority and recovery state. A saved materialisation is a draft basis, not an active production release.

Supply independent native expected cases and complete its proof and reviews. Check that the materialised outcome does not relax a tighter native rule or prerequisite. A changed source or definition revision needs another deliberate mapping and review.

If a request is uncertain, use Check unfinished requests and its original-result recovery before changing another input. Do not replace an unconfirmed mapping with a fresh command. Continue with [Understand release evidence](/manuals/automation/proof-and-release) for publication and [Coordinate policy sets](/manuals/automation/policy-sets) only where the complete reviewed relationship requires the supported coordinated lifecycle.