The 27 terms you'll see across EternityArc, in plain language.
- Golden record
- The single, trusted version of an entity (a customer, vendor, or provider) produced after matching and merging duplicates from every source system.
- Match & merge
- The MDM process that identifies likely-duplicate records across sources (fuzzy or exact) and consolidates them into one golden record.
- Survivorship
- The rule set that decides which source "wins" for each field when merging duplicate records — e.g. the most recently updated source, or a specific trusted system.
- Licence file
- The signed file you receive once a registration is approved. It names your tenant, your environment and exactly the modules you were granted, and it is the first thing the EternityArc setup wizard asks for.
- Orchestrator flow
- A defined sequence of jobs and dependencies that Orchestrator runs and monitors across modules, with run history and alerting.
- Attribute-level lineage
- A record of which source system contributed each individual field on a golden record, kept for audit and troubleshooting.
- Business entity
- One kind of entity you master — Customer, Product, Supplier — with its own columns, match rules and golden records.
- Landing & staging
- Where source data arrives before mastering: landing holds it as delivered, staging holds it cleaned and ready to load.
- Trust score
- How much a value is believed, based on the source that supplied it. Survivorship compares trust scores to pick each field's winner.
- Trust decay
- The penalty a value's trust score takes when it fails a validation rule, so bad data stops winning merges.
- Consolidation state
- Where a record is in the lifecycle: New, Validated, Matched, or Consolidated — the last one being a golden record.
- Match group
- A set of records the match rules scored above the threshold as the same real-world entity, ready to merge.
- Reference data
- Controlled lists — country codes, units, categories — that validation rules and lookups check values against.
- Environment
- A separate copy of the platform — DEV, QA or PROD — with its own database and its own user accounts.
- Business ID
- The identifier every record gets on intake, in one format you configure, so a record keeps the same ID from staging to golden record.
- Cross-reference
- A source system's own key, kept on the golden record, so systems downstream can keep using the IDs they already know.
- Match threshold
- The score a pair of records must reach to be grouped as the same entity. Pairs just below it wait for a steward.
- Data steward
- The person who resolves what rules can't: borderline matches, rejected rows and requests to unmerge.
- View 360
- The screen that shows a golden record with every contributing source record beside it, where stewards merge, unmerge and review.
- Unmerge
- Splitting a golden record back into the records it was built from. Field history is kept, so nothing is lost.
- Reject rule
- A rule applied at staging that holds back a row, with a reason, before it can reach matching.
- Trust matrix
- The per-source, per-field ranking that sets each value's starting trust score.
- Hierarchy
- Parent–child relationships between golden records — supplier to parent company, product to family — so reports can roll up.
- MCP server
- The Model Context Protocol endpoint AI agents connect to. Each agent uses its own API key and scope, and every call is audited.
- Privacy-safe mode
- The default for AI agents: personal and sensitive columns, and opted-out subjects, are withheld from anything an agent reads.
- AI suggestion
- A change an AI agent proposed rather than made. It waits in the approval queue until a steward accepts or rejects it.
- Approval workflow
- A review step that holds changes to chosen fields until a reviewer accepts them.
