Skip to content

v0.5.0 — Deterministic extraction

Choose a tag to compare

View all tags
@Bogzx Bogzx released this 09 Jun 20:39
· 10 commits to main since this release
v0.5.0
eb46b6e

Always reports the same thing — verified live on DeepSeek via OpenRouter.

  • Consensus voting ([llm] consensus_runs, default 3): each changed post is extracted N times, majority events kept. Hosted APIs are not deterministic at temperature 0 (OpenRouter routes one model id across providers); voting makes the result stable. Live proof: 4 consecutive consensus extractions of a real FTMO post -> identical event sets, identical event keys.
  • Prompt rule excluding Client Area/IT maintenance — the one borderline case that flickered between runs
  • Consensus identity merges timezone-attribution variants (explicit offset wins) so the vote never splits on equivalent events
  • seed hint on OpenAI-compatible calls
Assets 2
Loading