> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zwiron.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Golden records and write-back

> Build golden records from approved Match groups and write them back with Write back approved.

## Overview

When Match groups are **approved**, Zwiron can produce a **golden record** for each group using the project’s **Survivorship** settings. **Write back approved** on the run results hub upserts those golden rows to a destination table so downstream systems can use a single surviving record.

Write-back is started from the **run results hub**, not from sync Jobs under **Data → Jobs**.

***

## Survivorship

Configure survivorship on the Match project (**Edit**, create form, or **Advanced**):

| Setting | Values |
| - | - |
| **Survivorship** | **Longest non-empty**, **First populated**, **Source priority**, **Most recent** |
| **Timestamp field** | Required for meaningful **Most recent** behavior |
| **Source field** / **Source priority** | Used with **Source priority** |

On an approved group, stewards may **Edit golden** / **Save golden** before write-back, or **Regenerate golden** to rebuild from rules.

***

## Destination settings

On the project (**Show advanced scoring & write-back** or **Advanced**):

| Setting | Purpose |
| - | - |
| **Golden table** | Destination table for upsert. If blank, the product derives a `_golden` table name from the source table—confirm the resolved name on the project before write-back |
| **Destination connection** | Connection used for write-back (defaults to the source connection when unset) |

<Note>
  Write-back requires a usable destination (connection + table) and at least one approved golden. If write-back fails, verify destination permissions and that groups were approved (goldens exist for the run).
</Note>

***

## Write back approved goldens

To write back from a run:

1. Open the run results hub (**Match review** from **Match → Review**, or open the run from the project).
2. Ensure groups you intend to publish are **approved** (clear **For Review** for those groups).
3. Click **Write back approved**.
4. Confirm the success message (rows written and groups merged).
5. Optionally open **Reviewed**, or use overflow actions to **Export goldens CSV** / **Export groups CSV**.

<Note>
  **Write back approved** is disabled when there is nothing useful to write (for example all groups still pending and none reviewed). Approve groups first.
</Note>

***

## Catalog and Trust close-loop

If the Match project is linked to a **Catalog table**:

* Write-back records **Know** lineage for the movement of golden data
* **Trust** re-detect may run on that asset so quality and incidents stay current

If no Catalog table is linked:

* Golden rows are still written when write-back succeeds
* The Know / Trust close-loop is skipped (the product reports this in the write-back result note)

Link an asset on the project when you want the full Move → Know → Trust cycle after Match.

***

## Export without write-back

From the run hub overflow menu:

| Action | Content |
| - | - |
| **Export groups CSV** | Group identifiers, block keys, status, member counts, scores |
| **Export goldens CSV** | Golden field payloads by group |

Use exports for audit or offline review before or after write-back.

***

## Related articles

* [Match overview](/match/overview)
* [Match projects](/match/projects)
* [Match advanced settings](/match/advanced-settings)
* [Reviewing Match results](/match/review)
* [Catalog](/platform/catalog)
* [Trust overview](/trust/overview)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.