vamos-optimization 1.0.0__tar.gz

vamos_optimization-1.0.0/AUTHORS.md

@@ -0,0 +1,7 @@
+# Authors
+
+- Nicolás R. Uribe (Universidad Rey Juan Carlos, Spain)
+- Alberto Herrán (Universidad Rey Juan Carlos, Spain)
+- Antonio J. Nebro (University of Málaga, Spain)
+- Javier Del Ser (TECNALIA / University of the Basque Country UPV/EHU, Spain)
+- J. Manuel Colmenar (Universidad Rey Juan Carlos, Spain)

vamos_optimization-1.0.0/CHANGELOG.md

@@ -0,0 +1,71 @@
+# Changelog
+
+All notable public changes to VAMOS are documented here.
+
+## [Unreleased]
+
+No changes yet.
+
+## [1.0.0] - 2026-09-06
+
+VAMOS 1.0.0 is the first official public release and the first compatibility
+baseline. Earlier version strings and Git tags were internal pre-public
+development markers; they are not prior public releases.
+
+### Added
+
+- A stable top-level Python API for optimization, built-in problems, and typed
+  algorithm configuration objects.
+- Nine built-in multi-objective algorithms: AGE-MOEA, IBEA, MOEA/D, NSGA-II,
+  NSGA-III, RVEA, SMPSO, SMS-EMOA, and SPEA2.
+- NumPy as the deterministic reference backend, with optional Numba kernel
+  acceleration and MooCore indicator acceleration.
+- A canonical `RunManifest` lifecycle through `save_result`, `load_run`,
+  `load_result`, `verify_run`, and exact same-environment built-in `reproduce`.
+- A canonical `StudyManifest` lifecycle through `StudySpec`, `plan_study`,
+  `create_study`, `load_study`, and the `Study.run`, `inspect`, `summarize`,
+  `cancel`, `resume`, and `retry` operations.
+- Persisted failure policies, cooperative cancellation, interrupted-state
+  reconciliation, bounded retry, `StudyReport`, and `StudySummary` projections.
+- Stable CLI contracts for top-level optimization, run inspection,
+  verification and replay, and durable study planning and execution.
+- Guides for installation, first optimization, the run lifecycle, replay,
+  durable studies, Studio's trust boundary, stability, and known limitations.
+- Human contributor guidance and scoped `AGENTS.md` instructions for automated
+  coding agents working within the repository architecture.
+
+### Changed
+
+- Package metadata, runtime version, citation data, documentation, built
+  artifacts, and examples now derive from the single `1.0.0` release version.
+- The public compatibility policy now distinguishes stable, experimental, and
+  internal surfaces and defines the 1.x deprecation and security policies.
+- Studio is explicitly experimental. It binds to loopback by default, requires
+  an explicit remote-binding opt-in, and requires per-code-revision consent
+  before reviewed Python is executed as trusted local code.
+
+### Fixed
+
+- Evaluation-budget, seed ownership, backend selection, and artifact integrity
+  behavior are covered by focused compatibility and replay tests.
+- Loading, inspection, and verification reject unsafe paths, unsafe NPZ data,
+  malformed manifests, and excessive input before executing recorded code.
+- Study planning and recovery preserve deterministic task identity and a
+  single-writer journal across interruption, retry, and resume.
+
+### Compatibility and known limitations
+
+- Semantic-versioning commitments begin with this release. No reader or shim
+  is provided for internal pre-public artifacts.
+- Exact replay is limited to reconstructable built-in components in the same
+  materially relevant environment and backend; it does not install missing
+  dependencies or execute recorded custom Python.
+- Durable study mutation is single-owner. Concurrent writers, distributed
+  study execution, and cross-process cancellation are not supported in 1.0.0.
+- Cross-backend bitwise equality is not promised. Optional dependencies and
+  third-party integrations may have narrower platform support.
+- Studio, tuning, visualization, provider integrations, plugin interfaces, and
+  non-stable CLI commands remain experimental.
+
+[Unreleased]: https://github.com/vamos-optimization/VAMOS/compare/v1.0.0...HEAD
+[1.0.0]: https://github.com/vamos-optimization/VAMOS/releases/tag/v1.0.0

vamos_optimization-1.0.0/CITATION.cff

@@ -0,0 +1,22 @@
+cff-version: 1.2.0
+message: "If you use this software, please cite it as below."
+authors:
+- family-names: "Rodriguez Uribe"
+  given-names: "Nicolas"
+  affiliation: "Universidad Rey Juan Carlos, Spain"
+- family-names: "Herrán"
+  given-names: "Alberto"
+  affiliation: "Universidad Rey Juan Carlos, Spain"
+- family-names: "Nebro"
+  given-names: "Antonio J."
+  affiliation: "University of Málaga, Spain"
+- family-names: "Del Ser"
+  given-names: "Javier"
+  affiliation: "TECNALIA / University of the Basque Country UPV/EHU, Spain"
+- family-names: "Colmenar"
+  given-names: "J. Manuel"
+  affiliation: "Universidad Rey Juan Carlos, Spain"
+title: "VAMOS: Vectorized Architecture for Multiobjective Optimization Studies"
+version: 1.0.0
+date-released: 2026-09-06
+url: "https://github.com/vamos-optimization/VAMOS"

vamos_optimization-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# Contributing to VAMOS
+
+Thank you for considering a contribution! This project is organized to make adding new components straightforward.
+
+Open issues and pull requests in the [official repository](https://github.com/vamos-optimization/VAMOS).
+See [repository governance](docs/project/repository-governance.md) for source and mirror ownership.
+
+Repository-wide contributor and agent rules, including validation tiers and Git discipline, live in `AGENTS.md`. Nested `AGENTS.md` files add only local subtree rules.
+
+## Adding a new problem
+- Put the implementation under `src/vamos/foundation/problem/` (one file per problem family).
+- Register it by adding a spec to the correct family module under `src/vamos/foundation/problem/registry/families/`.
+- Add a short docstring to the problem class describing the landscape and encoding.
+- Add a small smoke test in `tests/` to validate instantiation and `evaluate` shape.
+- See `docs/dev/add_problem.md` for a step-by-step template.
+
+## Adding a new algorithm
+- Implement the vectorized core under `src/vamos/engine/algorithm/`.
+- Create a config dataclass/builder under `src/vamos/engine/algorithm/config/` to keep construction declarative and serializable.
+- Register the algorithm in `src/vamos/engine/algorithm/registry.py` so orchestration layers and the CLI can resolve it by name.
+- Add a minimal smoke test (tiny population/evaluation budget) to catch wiring issues.
+- See `docs/dev/add_algorithm.md` for a template and checklist.
+
+## Adding an operator or metric
+- Follow `docs/dev/add_operator.md` for variation/repair components.
+- Follow `docs/dev/add_metric.md` for quality indicators and metric ownership.
+
+## Adding a new kernel backend
+- Implement the `KernelBackend` interface in `src/vamos/foundation/kernel/` (see `kernel/backend.py` for required methods).
+- Register it in `src/vamos/foundation/kernel/registry.py` with a unique engine name.
+- Add a backend-marked smoke test (`@pytest.mark.<engine>`) that runs a small NSGA-II job; use `pytest.importorskip` to skip when the dependency is missing.
+- See `docs/dev/add_backend.md` for required methods and a smoke-test example.
+
+## Architecture health (mandatory)
+- Read the ADRs before any architectural change: `docs/dev/adr/index.md`.
+- Run the local fast-fail health command: `python tools/health.py`.
+- CI has a different platform/version and coverage scope. Both health and CI run `python tools/check_agent_docs.py` with identical arguments.
+- Typing has one entry point: `python tools/typecheck.py --scope strict|stable|full|release|full-zero`. Health and CI run strict and full. Release requires strict/stable zero, the exact full-source ratchet, and health; `full-zero` remains the visible global-zero roadmap gate.
+- If you change public APIs, update the snapshot: `python tools/update_public_api_snapshot.py`.
+
+## Continuous Integration
+- CI runs its configured matrix of lint, targeted mypy, architecture, test, docs, notebook, and build jobs.
+- Before opening a PR, run the applicable full tier from `AGENTS.md`:
+  - `python tools/health.py`
+  - `python -m pytest -q`
+  - `mkdocs build --strict`
+
+## Coding style and typing
+- The project uses a `src/` layout and prefers type hints on public-facing functions/classes.
+- Performance-critical loops (kernels, variation) should remain lightweight; avoid refactors that change behavior without explicit benchmarks.
+- Every changed production module must be clean under the canonical typecheck. New diagnostics and increased baseline multiplicity are forbidden.
+- Read `docs/dev/typing.md` for the pinned environment, strict/full/release semantics, and baseline-reduction procedure.
+- Read `docs/project/stability-and-versioning.md` before changing a stable API, CLI argument, configuration field, or public artifact schema.
+
+## Tuning package layout
+- All tuning utilities (parameter spaces, samplers, racing loop, random search) live under `src/vamos/engine/tuning/racing/`.
+- Import from `vamos.engine.tuning`. Do not document or depend on a `vamos.tuning` facade; it is not part of the public API.
+
+## Self-check
+- After changes, run `vamos check` for a quick sanity check.
+- CI-friendly tests live under `tests/`; keep populations/evaluation budgets small for speed.
+
+## Before opening a pull request (human or AI-assisted)
+1. Run the health gates: `python tools/health.py`.
+2. Run the full suite: `pytest -q`.
+3. If you touched tuning, durable studies, or benchmarking:
+   - Run the smallest relevant `vamos bench` suite.
+4. If you added docs or notebooks:
+   - Build docs with `mkdocs build --strict` and run the affected notebook smoke.
+5. For AI-assisted work, start at root `AGENTS.md`; use at most one scoped local instruction and one routed developer guide.

vamos_optimization-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 VAMOS contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

vamos_optimization-1.0.0/MANIFEST.in

@@ -0,0 +1,6 @@
+include LICENSE
+include README.md
+include CHANGELOG.md
+include CITATION.cff
+include AUTHORS.md
+include CONTRIBUTING.md