Skip to content

Releases: ddy6/looptimum

v0.4.0

26 Mar 20:03

Choose a tag to compare

full planned expansion of Looptimum’s file-backed optimization workflow, adding mixed-type and conditional search spaces, constraints, multi-objective support, batch/async worker flow, warm-start import/export, archive restore/prune, observability/governance, starter-kit integrations, and preview service/dashboard/auth/coordination surfaces.

v0.3.5

21 Mar 14:38

Choose a tag to compare

conditional parameters omission-aware end-to-end across suggest, ingest replay, duplicate handling, and report/CSV/state artifacts.

v0.3.4

21 Mar 12:54

Choose a tag to compare

closing phase 0 0.4.0 updates - removed legacy contract compatibility paths, centralized numeric search-
space behavior, aligned template config scaffolding for upcoming mixed-type search-space work.

v0.3.3

20 Mar 16:08

Choose a tag to compare

boto3-backed AWS Batch evaluator path and docs

v0.3.2

08 Mar 17:39

Choose a tag to compare

terminal_reason wiring, safe reset with archiving by default

v0.3.1

08 Mar 14:06

Choose a tag to compare

v0.3.1 Pre-release
Pre-release

Ingest behavior patched to handle null

Looptimum v0.3.0

06 Mar 15:26

Choose a tag to compare

Looptimum v0.3.0 Pre-release
Pre-release

v0.3.0

0.2x update program

05 Mar 00:50

Choose a tag to compare

0.2x update program Pre-release
Pre-release
  • New contract and operating docs: docs/operational-semantics.md, docs/search-space.md, docs/decision-trace.md, docs/pilot-checklist.md.
    
  • Lifecycle and ops command surface in templates: cancel, retire, heartbeat, report, validate, doctor.
    
  • Trial artifact manifests and event logging under state/trials/ and state/event_log.jsonl.
    
  • Trust-building assets: tiny objective loop, deterministic decision-trace samples, and transcript references.
    
  • CI quality gates for format/lint/internal-links and test matrix.
    
  • README and docs were rewritten to be mainstream-first and contract-forward.
    
  • Config and schema handling is now explicitly JSON-first with optional YAML support.
    
  • Ingest/state semantics were hardened across demo/default/full templates with explicit parity tests for contract-critical behavior.
    
  • Runtime state persistence now uses stronger locking and atomic-write patterns for mutating commands.