Decision Surfaces

Overview

A Decision Surface represents the type of operational decision you want FoxCommand to evaluate.

Choose the surface after you understand the customer workflow and before you submit mapped material to runtime capabilities.

Examples

If your customer workflow reviews prior authorization decisions, the Decision Surface should represent the prior authorization review scenario that your mapped material targets.

If your customer workflow reviews fraud signals, the Decision Surface should represent the fraud review scenario and the facts needed to evaluate it.

If your customer workflow reviews general decision outcomes, the Decision Surface should represent the decision review scenario and the customer-owned evidence that supports it.

These examples help organize customer material. They do not change runtime API behavior.

Why Surfaces Exist

Decision Surfaces help the customer integration keep three things aligned:

• The operational decision being evaluated.
• The Business Semantics that explain the customer meaning.
• The Decision Mapping that prepares FoxCommand-compatible inputs.

The surface gives the mapped material a clear target. Customer systems still own source facts, business meaning, and lifecycle decisions.

When To Choose A Surface

Choose a Decision Surface when:

• The customer decision is clear.
• Business Semantics are defined.
• The required Governance Artifact, policy setup, setup mapping, evidence, and traceability metadata are known.
• The integration is ready to map customer meaning into runtime-compatible inputs.

Relationship To Decision Mapping

Decision Mapping translates customer terminology and source facts into material that targets the selected Decision Surface.

For example, a prior authorization mapping might connect customer terms such as request, denial, medical necessity, policy version, and review state to the Governance Artifact, policy setup, setup mapping, and traceability metadata used for runtime evaluation.