Settlement
Watch.

Absence is not evidence while a feed is still behind.

A marketplace has a capture in its internal ledger but no matching processor capture. The processor export may be delayed. If the operations team raises an exception too early, it creates noise; if it waits forever, it misses real discrepancies.

Use both sources’ watermarks to mature a decision.

The engine correlates ledger and processor events by tenant and payment. It waits until each source watermark passes an event-time grace window before declaring an exception. A late processor event can resolve the discrepancy, and the correction stays visible in the payment history.

• Integer minor units protect monetary comparisons from floating-point errors.
• Duplicate event IDs are idempotent; conflicting duplicates are rejected.
• Atomic batch ingestion avoids partially accepted imports.
• Events require explicit timezone offsets.

Separate a replay from a throughput claim.

The live browser worker can generate a deterministic million-event synthetic replay so visitors can see ingestion progress, anomaly counts, watermark maturation, and late correction. The Python/SQLite engine has its own measured local benchmark and tests. The browser replay is not a distributed production workload.

An optional AI triage adapter produces a bounded internal brief only for mature exceptions. Code checks the structured output and citations; a person must verify its language.

ENGINE

Python · SQLite · event-time reconciliation

DEMO

Browser worker · synthetic event stream

BOUNDARY

No transfers, payouts, or live payment data

Watch an exception appear, then resolve.

Open the replay, run the synthetic stream, inspect a missing processor capture after the watermarks advance, and apply a late correction. The hosted interface runs locally in the visitor’s browser. It has no shared backend or real processor connector.

REFERENCE SYSTEM · SYNTHETIC PAYMENTS · NO CUSTOMER DEPLOYMENT OR REAL MONEY MOVEMENT