Skip to main content
Lattora 2.1.0 has four compiled-in algorithms. It has no public plugin loader or algorithm registration command. The shared contract #23 and reviewed onboarding #26 remain planned.

​
Start with a small source change

  1. Trace the existing engine path. Check its callers and validator assumptions.
  2. Define the algorithm/model identity, objective, units, parameters, seeds, feasibility rules and budget.
  3. Reuse the ledger, evaluator, repair, simulation, metrics and output writers.
  4. Check a tiny known-answer case, invalid placements, deterministic seeds and budget accounting.
  5. Run a bounded paired trial through the packaged path. Keep failures, hashes, settings and validation evidence.
A new algorithm or model needs a separately identified experimental protocol/schema. The frozen four-algorithm matrix and CSV contracts do not expand automatically. Keep frozen behavior and saved evidence intact. Correctness checks do not establish novelty or superiority.

​
Scope the research work

Current Stress varies scale and search effort under one static model. General scenario families and selectable objectives remain planned. Reservation limits are not network/storage contention measurements. A zero-SLA model cannot demonstrate SLA optimization quality. Held-out tuning must predeclare separate tuning/confirmation inputs, selection rules, compute budgets and failed-trial treatment. Frozen sensitivity does not prove optimal N/T settings. Follow the capability roadmap and contribution gates. Update this guide when the implemented contract changes.