AI Ingestion
Temporal Normalization
To maintain ledger integrity, the appliance enforces a strict bitemporal distinction. Every entry is stamped with two separate temporal markers. This separation allows the system to distinguish between a business claim and the physical moment of observation.
The Bitemporal Markers
The protocol utilizes dual-clock verification to ensure that the "When" of the business logic never compromises the "When" of the audit record.
-
01
Recorded Date (recorded_dt) The user-defined moment an event occurred. It is the primary value used for historical reporting, business logic, and legitimate retroactive ledger entries.
-
02
Witnessed Date (witnessed_dt) The immutable, system-generated timestamp representing the exact microsecond the appliance sealed the record. This serves as the "True North" for sequence purity.
-
03
The Invariant Rule The system enforces a rule where recorded_dt must be less than or equal to witnessed_dt. A record cannot claim to have occurred in the future relative to the moment it was witnessed.
Data Format Standardization
The appliance automatically normalizes disparate input formats to ensure a consistent historical record, allowing National Five Partners to integrate various client systems without manual pre-processing.
-
01
Multi-Format Resolution The system detects and normalizes Unix Microseconds, Unix Seconds, and ISO8601 Strings upon ingestion.
-
02
Precision Up-sampling Inputs provided in seconds or milliseconds are scaled to microsecond precision (1,000,000 units per second) to match the internal ledger schema.
-
03
UTC Standardization All incoming timestamps are converted to UTC. The system stores only the absolute point in time to ensure global consistency across different jurisdictions.
Clock Skew and Future-Post Protection
In distributed environments, minor time differences between servers are inevitable. The appliance utilizes a validation gate to absorb these jitters while protecting the ledger from significant temporal errors.
-
01
Configurable Leeway The system allows for a "Future-Post Buffer" (defaulting to 5,000 milliseconds) to accommodate high-frequency environments or specific network latencies.
-
02
Safe Convergence If a recorded_dt arrives within the authorized buffer, the system performs a safe convergence, automatically snapping the event to the current witnessed_dt.
-
03
Hard Rejection Entries exceeding the buffer result in a future_posting_violation. The system rejects the write and provides metadata for diagnosing upstream clock drift or logic errors.
Temporal Normalization
To maintain ledger integrity, the appliance enforces a strict bitemporal distinction. Every entry is stamped with two separate temporal markers. This separation allows the system to distinguish between a business claim and the physical moment of observation.
The Bitemporal Markers
The protocol utilizes dual-clock verification to ensure that the "When" of the business logic never compromises the "When" of the audit record.
-
01
Recorded Date (recorded_dt) The user-defined moment an event occurred. It is the primary value used for historical reporting, business logic, and legitimate retroactive ledger entries.
-
02
Witnessed Date (witnessed_dt) The immutable, system-generated timestamp representing the exact microsecond the appliance sealed the record. This serves as the "True North" for sequence purity.
-
03
The Invariant Rule The system enforces a rule where recorded_dt must be less than or equal to witnessed_dt. A record cannot claim to have occurred in the future relative to the moment it was witnessed.
Data Format Standardization
The appliance automatically normalizes disparate input formats to ensure a consistent historical record, allowing National Five Partners to integrate various client systems without manual pre-processing.
-
01
Multi-Format Resolution The system detects and normalizes Unix Microseconds, Unix Seconds, and ISO8601 Strings upon ingestion.
-
02
Precision Up-sampling Inputs provided in seconds or milliseconds are scaled to microsecond precision (1,000,000 units per second) to match the internal ledger schema.
-
03
UTC Standardization All incoming timestamps are converted to UTC. The system stores only the absolute point in time to ensure global consistency across different jurisdictions.
Clock Skew and Future-Post Protection
In distributed environments, minor time differences between servers are inevitable. The appliance utilizes a validation gate to absorb these jitters while protecting the ledger from significant temporal errors.
-
01
Configurable Leeway The system allows for a "Future-Post Buffer" (defaulting to 5,000 milliseconds) to accommodate high-frequency environments or specific network latencies.
-
02
Safe Convergence If a recorded_dt arrives within the authorized buffer, the system performs a safe convergence, automatically snapping the event to the current witnessed_dt.
-
03
Hard Rejection Entries exceeding the buffer result in a future_posting_violation. The system rejects the write and provides metadata for diagnosing upstream clock drift or logic errors.