EM-XCT-08 · Shared contract · W0
Sources, bindings and synchronization
Description of a master system, physical binding, extraction, snapshot, watermark and conflict. Local addresses and credentials are not published in the shared library.
Partially published; research continues
Claude: study-s1-s2-and-r4-r4a-audits-complete; Grok: study-s1-s2-and-r4-r4a-audits-complete.
Published results
Research note, in Russian: EM-XCT-08 remains partial: live source connectors and authenticated source guarantees; durable full extraction-attempt telemetry; production IAM/disclosure and evidence custody; EFA/EAP adapters; partitioned or distributed delivery; quarantine resolution, retention/erasure; capacity rollover, nonempty-bootstrap recovery and current-store continuity; production storage/throughput; existing-Dimension migration. Each needs a separately bounded implementation and acceptance.
Subject boundary and candidate types
- SourceSystem
- SourceBinding
- ExtractionRun
- SyncCursor
- SyncConflict
Deep research questions
- How to detect deletion and relocation of a source?
- How to match a Jira project to a business project?
- How to reproduce an import without a hidden change of meaning?
Verifiable invariants
- A binding is not a subject model
- A snapshot fixes its coverage
- A repeated import is idempotent
End-to-end acceptance scenario
A repeated import, deletion and renaming of a container preserve object IDs and explicit conflicts.
Negative case
Every new tracker board automatically creates a new business project.
Approaches to compare
- Current Vercy protocol/MMAS/whole-object and the published WM-XCT
- W3C PROV/SKOS/SHACL/ODRL where applicable
- Practice of source connectors, versioned schemas and policy enforcement
Candidates in the live catalogue
- WM-XCT-001 · Ownership / Stewardship · 0.3.1-enterprise.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-012 · Provenance · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.