← Back to catalogue
Published

Enterprise Source Synchronization

vr.profile.enterprise-source-synchronization · enterprise-source-synchronization

Connect qualified source records to existing company subjects, preserve immutable intake evidence and explain synchronization progress without inventing identity or deletion.

Enterprise profiles Cross-cutting context EnterpriseSources and integration
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

5 bundles · 10 layers · 27 findings · 54 questions

Sources Sources questions, evidence and guarded decisions.

Source identity

Source identity of a source synchronization register.

Source instance

Immutable SourceInstance declaration and continuity evidence

  1. Which actual tenant and environment emits these records? host-guidance
  2. What evidence distinguishes a restored or recreated instance? host-guidance

Qualified keys

Source, resource, scheme/version, exact key and record generation

  1. What qualifies this local record key? host-guidance
  2. Are lexical differences or recycled keys being hidden? host-guidance

Continuity

Generation evidence with source or authorized steward attribution

  1. Is the record generation known? host-guidance
  2. Who can attest non-reuse or an incarnation? host-guidance

Acquisition interpretation

Acquisition interpretation of a source synchronization register.

Scope boundary

Immutable scope and literal evidence-reference fingerprint

  1. Which filter, projection and visibility does this acquisition cover? host-guidance
  2. Did interpretation or schema change? host-guidance

Opaque progress

Protected token reference, local epoch, fence and head

  1. What exact source position was retained? host-guidance
  2. Is a token reset being confused with record rebirth? host-guidance
Mappings Mappings questions, evidence and guarded decisions.

Aboutness governance

Aboutness governance of a source synchronization register.

Subject meaning

Governed target catalogue and source-kind/target-kind/purpose pair

  1. Which existing subject is this record about? host-guidance
  2. Is a source board being mistaken for a business Project? host-guidance

Lifecycle

Proposed, active, disputed or retracted revisions with activation guard

  1. Which mapping revision is active? host-guidance
  2. Can a disputed claim reactivate beside another active claim? host-guidance

Replacement

New mapping identity, correction predecessor and retained history

  1. Which earlier mapping is being corrected? host-guidance
  2. Has the earlier claim been retracted first? host-guidance

Pinned interpretation

Pinned interpretation of a source synchronization register.

Historical outcome

Occurrence mapping/state, catalogue and policy revision pins

  1. Which mapping applied at first admission? host-guidance
  2. Will a later correction silently repin old data? host-guidance

Suspension

Current catalogue/validity check within the receiving scope and active-pin-suspended outcome

  1. Does the current target kind still satisfy the mapping? host-guidance
  2. Does a suspended claim still reserve its lineage? host-guidance
Intake Intake questions, evidence and guarded decisions.

Atomic delivery

Atomic delivery of a source synchronization register.

Batch identity

Scope/epoch-wide key and exact ordered content digest

  1. What identity survives a retry and a writer replacement? host-guidance
  2. Has content changed under the same key? host-guidance

Commit boundary

One local SQLite transaction and retained acknowledgement

  1. Were metadata, receipt and progress committed together? host-guidance
  2. Could a crash expose a head without its records? host-guidance

Concurrency

Serialized transaction and restricted conflict diagnostic

  1. Which expected head and fence admitted this new batch? host-guidance
  2. Does a stale writer advance progress? host-guidance

Partial failure

Partial failure of a source synchronization register.

Quarantine

Durable restricted quarantine evidence and open retry obligation

  1. Which input descriptors were rejected? host-guidance
  2. Do received counts equal retained accepted plus quarantined counts? host-guidance

Empty versus missing

Explicit empty flag, contiguous page indices and terminal marker

  1. Was an empty page explicitly delivered? host-guidance
  2. Are missing pages or transport failures being treated as an empty source? host-guidance
Evidence Evidence questions, evidence and guarded decisions.

Time and availability

Time and availability of a source synchronization register.

Three clocks

Nullable sourceEventTime, declared observedAt, trusted recordedAt and sequence

  1. When did the source event, acquisition and host receipt occur? host-guidance
  2. Was an unknown source time invented? host-guidance

Occurrence correction

Earlier occurrence reference, known lineage and steward admission

  1. Which retained occurrence is corrected? host-guidance
  2. Is correction lineage and attribution valid? host-guidance

Source availability

Explicit source-availability operation

  1. Was a source record deleted, removed from scope or inaccessible? host-guidance
  2. Does that authorize retirement of a business subject? host-guidance

Coverage assessment

Coverage assessment of a source synchronization register.

Round completion

Sealed terminal round and separate consistency/visibility declarations

  1. Were all pages accounted for without quarantine or unknown keys? host-guidance
  2. Does this prove that the external source is actually complete? host-guidance

Comparable absence

Explicit not-earlier witness and complete source-snapshot rounds

  1. Are two rounds of the same scope genuinely ordered and comparable? host-guidance
  2. Could visibility or a new interpretation explain the missing key? host-guidance

Competing evidence

Both retained evidence references and separately governed selection policy

  1. Do different sources disagree about a subject? host-guidance
  2. Which separate authority contract can adjudicate those facts? host-guidance
Operation Operation questions, evidence and guarded decisions.

Rights and custody

Rights and custody of a source synchronization register.

Current permission

Current exact host grant and authenticated actor

  1. Can this actor intake, map, read or attest coverage for this purpose now? host-guidance
  2. Does bootstrap administration imply ordinary writer permission? host-guidance

Restricted disclosure

Current read decision, protected projections and documented key-unavailability bit

  1. Can this result or diagnostic be disclosed now? host-guidance
  2. What can a competing authorized writer infer from refusal? host-guidance

Evidence custody

Host-managed protected evidence references

  1. Where are payloads, tokens and verification evidence stored? host-guidance
  2. Does a submitted digest prove they exist or are safe? host-guidance

Adoption and recovery

Adoption and recovery of a source synchronization register.

Native binding

One register object, snapshot facts and explicit extension validation

  1. Does the stored snapshot preserve the full semantic journal? host-guidance
  2. Did installed companion validation run after outer checks? host-guidance

Restore continuity

External ownership/current-root evidence and historical-only import report

  1. Is this the current owned database or a coherent old copy? host-guidance
  2. Can an archive legitimately resume an external token? host-guidance

Minimum profile

Synthetic startup, international and AI cases with explicit limits

  1. Which small source/mapping boundary is useful today? host-guidance
  2. Which enterprise capabilities are still deferred? host-guidance

Classifiers Filled

Family
Enterprise profiles
Category
Cross-cutting context
Entry kind
companion-contract
Navigation path
NAV.XCT
Domain
EnterpriseSources and integration
Industry
Cross-industry
Tags
EM-XCT-08sourcemappingsynchronizationcheckpointprovenancequarantine
Also called
EM-XCT-08, RecordSubjectMapping, SourceInstance, Sources, bindings and synchronization, SyncEpoch

What it is Filled

A companion contract for a Company Dimension that connects records from qualified sources to existing company subjects by proposal, keeps immutable intake evidence per batch, and explains synchronization progress without inventing identity or deletion.

Why it exists Filled

Connect qualified source records to existing company subjects, preserve immutable intake evidence and explain synchronization progress without inventing identity or deletion.

Distinguishing features Filled

  • Connects source records to existing company subjects by proposal, never by creating or merging subjects.
  • Keeps immutable intake evidence for every batch, including rejected descriptors.
  • Treats missing coverage as unknown, never as deletion.

What robots and AI may and may not do Filled

Must not

  • Infer identity from a display name.
  • Create or merge business subjects during intake.
  • Treat a record missing from a feed as deleted.
  • Silently accept changed content under an old key.

Only with a human decision

  • Confirming a proposed match when evidence is ambiguous.
  • Retiring a source instance generation.

May

  • Propose that a source record is about an existing subject.
  • Retry an intake with the same content and key after a lost response.
  • Report synchronization progress per scope.

Moral aspects Filled

  • Wrong matches merge two people's records and can expose one person's data to another.
  • Treating absence as deletion can erase someone's rights or history.

Who is affected

  • People and organizations whose records are synchronized
  • Data stewards resolving matches

Owners Filled

Steward

The integration owner runs synchronization; each source stays owned by its operator and each subject by its domain owner.

Master systems

  • Source systems
  • Master data hub of the subjects

Links to other meta-models Filled

references

  • WM-XCT-001 - 0.3.1-enterprise.1
  • WM-XCT-012 - 0.3.0-research.1

aligned

  • vr.wm-xct-001
  • vr.wm-xct-012

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Source instance generation ID.
  • Lexical source key kept byte-exact with its namespace.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: it has no physical body to measure.

Recognition optional Filled

  • A synchronization record ties a source descriptor and batch to a proposed subject with evidence.

Capabilities and actions required Filled

  • Register a new instance generation only after host verification. Requires applicable host authority.
  • Preserve lexical bytes and namespace; never infer identity from a display name. Requires applicable host authority.
  • Keep unknown continuity unpinned; do not invent a generation. Requires applicable host authority.
  • Create a new scope for changed interpretation; do not compare incompatible coverage. Requires applicable host authority.
  • Treat tokens as opaque; a new epoch does not itself change business identity. Requires applicable host authority.
  • Propose aboutness only; do not create or merge business subjects. Requires applicable host authority.
  • Check complete-lineage/purpose uniqueness on every activation. Requires applicable host authority.
  • Retract the old claim before activation; a temporary zero-active interval is allowed. Requires applicable host authority.
  • Keep the original outcome immutable; inspect later revisions separately. Requires applicable host authority.
  • Withhold new pins and preserve the active uniqueness reservation until steward action. Requires applicable host authority.
  • Reuse exact content/key after a lost response; never silently accept changed content. Requires applicable host authority.
  • Use the owned local store; external payload durability remains a host responsibility. Requires applicable host authority.
  • Refuse stale new admissions; an authorized exact own retry returns its old acknowledgement. Requires applicable host authority.
  • Retain each rejected descriptor; resolve externally and reingest with a new batch. Requires applicable host authority.
  • Keep missing coverage insufficient; do not infer business deletion. Requires applicable host authority.
  • Preserve unknown source time and compare only the appropriate clock. Requires applicable host authority.
  • Append correction evidence; keep the old occurrence unchanged. Requires applicable host authority.
  • Retain availability evidence without changing the subject lifecycle. Requires applicable host authority.
  • Distinguish strong local key accounting from a verified source guarantee. Requires applicable host authority.
  • Emit only a steward-review proposal and no effects. Requires applicable host authority.
  • Do not let arrival order or connector ownership choose business truth. Requires applicable host authority.
  • Check each right independently; never derive permission from semantic source priority. Requires applicable host authority.
  • Keep full archives privileged; acknowledge the residual availability side channel. Requires applicable host authority.
  • Verify custody externally; the reference neither fetches nor authenticates payload bytes. Requires applicable host authority.
  • Validate both envelopes and nested history; the snapshot is a restricted projection. Requires applicable host authority.

Hazards and failure modes required Filled

  • False merges of distinct subjects.
  • False deletions from partial feeds.

Standards and interfaces required Filled

  • Change data capture feeds.
  • Entity resolution practice.

Context of use required Filled

  • Integration of external and internal systems into one Company Dimension.

Sources Filled

  1. Research record EM-XCT-08: independent provider studies, audits and reconciled findings - Evidence behind the release; claims in the card trace to it.
  2. Enterprise Source Synchronization 0.1.0 specification - Normative release, digest sha256:8dbb0293e00ca971d54a86b81b4baae9a41ed4f88e7f7012fb477eabd89d0203

Open questions

  • Use the pinned companion schema/validator and trusted-host binding. Native outer validation alone does not enforce nested semantics. Consult the released adoption limits. Start with SourceInstance, qualified acquisition scope and steward-reviewed aboutness to existing subjects. Metadata intake never creates or retires business subjects. Executable use needs trusted host identity, grants, time, evidence custody and current local-store ownership. Read the finite-capacity, shared-page, disclosure and recovery limits before installation. Required reading: https://ver.cy/models/enterprise-source-synchronization/versions/0.1.0/publication-addendum.md

Machine files

Card as JSON Specification AGENTS.md Package Source Card backlog vercy.card/1

Provenance

enterprise research · reviewable-draft

Built from: models/enterprise-source-synchronization/versions/0.1.0/spec.json, models/enterprise-source-synchronization/catalogue-entry.json, ver-cy/world-models/card-supplements/enterprise-source-synchronization.json