Skip to content

Continuous loop: scheduled ingest → re-backtest daemon (ambient operation) #26

Description

@aktasbatuhan

Everything today is one-shot CLI: import, curate, experiment, gate are each a human keystroke. The positioning promise — a switch verdict that stays fresh while you sleep — needs an ambient lane.

  • A scheduler/daemon mode (compound watch or similar): periodic Langfuse sync from a high-water mark, incremental curation pass, then cache-replay of standing candidates against fresh incumbent traces — an offline shadow: the candidate is continuously graded on new production requests without touching the serving path.
  • A re-gate policy: how much new sealed-eligible data (or drift) triggers a re-decision, so gates re-run on evidence, not on a timer.
  • Strictly offline/control-plane: no proxying, no live traffic split (that is a later, separate arc).

Depends on: auto-curation policy (continuous ingest is pointless if every case waits on human review) and verdict-freshness metadata (the trigger signal).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions