dv-xts

Detect and correct out-of-sequence satellite data by persisting staged hashdiffs.

35|7|Updated Apr 14, 2022
One-click install
npx skills add https://github.com/PatrickCuba/the_data_must_flow --skill dv-xts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dv-xts
Source: https://github.com/PatrickCuba/the_data_must_flow/tree/main/dvos-skills/skills/dv-xts
Command: npx skills add https://github.com/PatrickCuba/the_data_must_flow --skill dv-xts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

XTS addresses the time-crime problem in Data Vault loading by capturing every staged hashdiff (including duplicates) and applying a timeline correction when late-arriving data is detected.

Core Features & Use Cases

  • Tracks every staged hashdiff for a hub or link satellite to ensure a correct historical timeline.
  • Provides SWITCH-based out-of-sequence detection and two load paths: XTS-assisted (copy/insert) and standard hashdiff load.
  • Supports audit-friendly timeline corrections and data-visibility improvements in environments with late feeds or data reprocessing.

Quick Start

Stage your data, set the SWITCH, insert into SAT_XT_HUB_<PARENT>, and run the appropriate load path (XTS-assisted or normal) based on the SWITCH result.

Frequently Asked Questions about dv-xts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I correct late-arriving data in Data Vault satellite loads?

To correct late-arriving data in Data Vault satellite loads, you persist all staged hashdiffs and apply timeline corrections. This approach detects out-of-sequence records and uses SWITCH-driven copy or insert events to preserve historical accuracy.

What is the time-crime problem in Data Vault and how do staged hashdiffs help?

The time-crime problem in Data Vault occurs when late-arriving data disrupts historical sequence. Persisting every staged hashdiff, including duplicates, captures the full timeline and enables targeted corrections to restore data visibility and audit accuracy.

How do I set up XTS-assisted loading for hub and link satellites?

To set up XTS-assisted loading for hub and link satellites, stage your data and configure dedicated dv_rectarget entries. Set the SWITCH, insert records into SAT_XT_HUB_<PARENT>, and run either the XTS-assisted or standard hashdiff load path based on the result.

Does timeline correction for late feeds preserve the existing audit trail?

Yes, timeline correction for late feeds preserves the audit trail by utilizing both insert and copy events. This ensures that all adjustments to out-of-sequence satellite data maintain full historical visibility and compliance within the Data Vault workflow.

When should I use the XTS-assisted load path instead of a standard hashdiff load?

Use the XTS-assisted load path instead of a standard hashdiff load when you need to process out-of-sequence or late-arriving data. A SWITCH mechanism evaluates the staged data to determine if timeline corrections are necessary before applying the appropriate load.

What are the limitations of using SWITCH-based out-of-sequence detection for satellites?

SWITCH-based out-of-sequence detection requires dedicated dv_rectarget entries for each hub and link satellite. Proper configuration of the XTS table and SAT_XT_HUB_<PARENT> is mandatory, meaning standard implementations without these artifacts cannot perform timeline corrections.