# Configuration
The Configuration panel defines what goes into a Digital Twin: the data it runs on, the variables included in causal discovery, the algorithms used, and any prior knowledge about which relationships are known or impossible. Get this right and discovery has a fair chance. Get it wrong and you'll miss real effects or fabricate spurious ones.
The panel is read-only by default. Click **Edit & Create New Version** at the top right to make changes; every save creates a new version of the twin and retrains.
For context, see [Step 5: Build Digital Twin](/user-guide/creating-digital-twin.md) and [Exploring the Causal Model](/more-details/digital-twin/exploring-causal-model.md).
***
## Opening Configuration
In the Overview panel's **Config** section, click the *View Config* link. The graph stays visible on the left; the right panel switches to the Configuration view.
The Configuration panel against the DAG view. All six sections are read-only until you click Edit & Create New Version.
***
## Data View
The dataset the twin is built from. Changing it triggers a new **major** version, because the twin is now based on different data.
***
## Fields
Every column from the Data View, with its data type (Boolean, Category, Number, Date/Time, Array/Set). The header shows the include count ("20 included, 1 excluded" in the example). Use the filter at the top to find a field by name; toggle each field to include or exclude.
Exclude:
* **Unique identifiers** (customer\_id, order\_id) — no causal meaning.
* **Metadata** (created\_at, updated\_by) — usually irrelevant.
* **Redundant fields** that duplicate another column.
Include anything you might want to predict, simulate, or trace a causal path through.
***
## Algorithm Versions
Two algorithm choices, one per stage:
* **Causal Discovery** — builds the graph. Default: **SPARC** (adaptive multi-stage).
* **Digital Twin** — fits the probabilistic model on top. Default: **CausalBART** (Bayesian network simulation).
***
## Variable Roles
Variable Roles fence off the ends of the causal chain:
* **Sources (exogenous)** — pure drivers. Only other sources are allowed to influence them.
* **Targets (outcomes)** — pure outcomes. They can only send edges to other targets.
Variables not marked are free to be cause or effect, in either direction. In the example, customerID, InternetService, MultipleLines, and PhoneService are sources; Churn is the target.
***
## Prior Knowledge
Encode certainty about specific edges before discovery runs:
* **Known relationships** — edges that must exist. Use when you have experimental evidence or domain certainty.
* **Blocked relationships** — edges that cannot exist. Use when a connection is logically impossible.
Both lists are optional; both improve the resulting graph when you have real prior knowledge to add.
***
## Variable Ordering
Constrains causal precedence at the variable level. *"TechSupport must come after InternetService"* tells discovery that TechSupport cannot be a cause of InternetService — only an effect, direct or indirect. Useful when temporal order is known or domain logic is clear.
***
## What happens when you save
Click **Edit & Create New Version**, change what you need, save. A new version of the twin is created and causal discovery reruns against the updated configuration. The form warns whether your edit will produce a new **major** version (Data View change) or a **minor** version (everything else).
***
## Other Working with a Digital Twin pages
* [Exploring the Causal Model](/more-details/digital-twin/exploring-causal-model.md) — graph layouts and variable details.
* [Reviewing Model Quality](/more-details/digital-twin/model-quality.md) — predictive accuracy and per-variable metrics.
* [Inspecting Causal Relationships](/more-details/digital-twin/causal-relationships.md) — individual edges and their statistics.
* **Version History** *(coming soon)* — multiple versions of the same twin.
See [Digital Twin overview](/more-details/digital-twin.md) — general overview.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.rootcause.ai/more-details/digital-twin/configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.