Skip to main content

Source Pressure Reference

Metadata​

  • Owner: Origo Engineering
  • Last updated: 2026-04-14
  • Slice/version reference: S50

Purpose and scope​

  • User-facing and operator-facing reference for the declared source-pressure contract across live pull sources.
  • This registry is declaration authority only. Runtime enforcement remains in the existing source-specific loaders, jobs, clients, sensors, and proof/quarantine surfaces.

Canonical registry​

  • Registry path: contracts/source-pressure-v1.json
  • Python source: origo/events/source_pressure.py

What counts as a source-pressure subject​

  • one declared pull-source subject that can distress independently
  • subject scope kinds:
    • canonical_stream
    • source_runtime
    • endpoint

Current live subjects​

  • binance_spot_trades
  • bybit_spot_trades
  • okx_spot_trades
  • okx_download_link_resolution
  • etf_scraper_fetch
  • fred_api_fetch
  • bitcoin_core_rpc

Distress triggers​

  • timeout
  • upstream_rate_limit
  • retry_budget_exhausted
  • declared_source_safe_limit_violation
  • source_contract_or_availability_failure

Fixed controls​

  • http_timeout
  • rpc_timeout
  • min_request_interval
  • source_safe_concurrency_ceiling
  • worker_pool_size
  • fixed_retry_policy
  • request_window_size

Operator-visible surfaces​

  • dagster_run_failure
  • dagster_sensor_or_alert
  • runtime_audit_event
  • proof_or_quarantine_state

Boundaries​

  • Downstream store-client limits and orchestrator-global limits are not source-pressure declarations.
  • Current live subjects are all pull.
  • Push-source admission remains blocked until Origo has a durable platform-owned accept-then-drain buffer contract.
  • Retaining raw source artifacts is not enough to qualify as a push buffer.