The curated description survives the harvest. This is the single most important runtime behaviour in the system — every stewardship hour depends on it.
The watermark advances only after a successful commit, so a failed run re-reads rather than skips.
Rate limiting is handled by backoff inside the connector, not by failing the workflow; the orchestrator sees a slow run, not a broken one.
Numbers
Incremental harvest of a 50,000-table warehouse completes in under 20 minutes.
Peak sustained ingest 5,000 change proposals per second during a full-estate rebuild.
Assumption
Sources expose a reliable change marker — an information-schema timestamp, a system table or a log offset. Sources without one fall back to full harvest on the weekly schedule.
