sprint-0: fundaciones VMS-Sailor
Sprint 0 completo del producto VMS-Sailor (Vessel Management System integrado para buques 30-40m). Brief de referencia en VMS_Sailor_v2_Parte_*.md (intacto). Core (vmssailor.core, 95.17% coverage, 99 tests verde): - ShipCoord: sistema naval x_pp/y_cl/z_bl frozen - Vessel, Deck, Bulkhead - Equipment, EquipmentModel, Sensor, EquipmentSpec - Tag, AlarmConfig, TagBinding, Scaling - CardInstance, Bus, Topology con validacion 21 puntos I/O AR-NMEA-IO-v1.0 - Alarm, PermissiveRule, Condition - Project agregado raiz con validacion cross-entity - Persistencia portable .vmsproj (SQLite) con roundtrip verificable Biblioteca curada seed (vmssailor.library): - systems_catalog.json completo (catalogo maestro Parte 1 sec 7) - 2 vessels: Sunseeker 76, Ferretti 850 - 2 motores: MTU 12V 2000 M96, Volvo D13-900 - 1 genset: Northern Lights M65C13 - yacht_motor_planeo.yaml (reglas heuristicas) - TODO marcado data_source=seed_estimate - requiere validacion datasheets Tools: - vms-validate-library: CLI valida biblioteca completa - vms-generate-test-project: CLI demo + verificacion roundtrip persistencia Design System + 8 mockups HTML estaticos: - docs/design_system.md (paleta Deep Ocean, gradientes, typography, motion) - docs/brand/ (logo + variantes SVG) - docs/mockups/splash, studio_main, runtime_overview, runtime_mimic_fuel (P&ID animado), runtime_alarms, runtime_trim (panel estrella con horizonte artificial), mobile_overview, mobile_trim - docs/mockups/index.html (galeria) Firmware (Sprint 12+ implementacion): - firmware/ar_nmea_io_v1/src/config/pinout.h con macros GPIO Decisiones autonomas documentadas en docs/decisions_sprint0.md. Stack: Python 3.11 + uv + Pydantic v2 + SQLite stdlib + hatchling + pytest 9 + ruff + mypy. Sin PySide6, FastAPI, Flutter ni firmware funcional (entran en sprints siguientes). Criterio de aceptacion Sprint 0: cumplido. - uv sync: OK - pytest: 99/99 verde - cov vmssailor.core: 95.17% (objetivo >=80%) - ruff: clean - vms-validate-library: OK - vms-generate-test-project: INTEGRIDAD OK Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
+31
@@ -0,0 +1,31 @@
|
||||
VMS-Sailor — Vessel Management System
|
||||
Copyright (c) 2026 Álvaro (Aerom). All rights reserved.
|
||||
|
||||
PROPRIETARY AND CONFIDENTIAL.
|
||||
|
||||
This software, including its source code, binaries, configuration files,
|
||||
curated library (vessel templates, equipment catalogs, heuristic rules,
|
||||
mimics), firmware, mobile application, and accompanying documentation
|
||||
("the Software"), is the proprietary intellectual property of Álvaro.
|
||||
|
||||
NO LICENSE TO USE, COPY, MODIFY, DISTRIBUTE, SUBLICENSE, OR CREATE DERIVATIVE
|
||||
WORKS IS GRANTED EXCEPT BY EXPRESS WRITTEN AGREEMENT WITH THE COPYRIGHT
|
||||
HOLDER.
|
||||
|
||||
The Software is distributed to end customers only in compiled, signed,
|
||||
HWID-bound packages ("VMSPACK", "VMSDELTA"). Any inspection, reverse
|
||||
engineering, decompilation, or extraction of the curated library content
|
||||
is strictly prohibited.
|
||||
|
||||
The Studio component MUST NOT be distributed to customers under any
|
||||
circumstance. The Studio license is hardware-bound to the development
|
||||
machines authorized by the copyright holder.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND. THE
|
||||
COPYRIGHT HOLDER SHALL NOT BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER
|
||||
LIABILITY ARISING FROM USE OF THE SOFTWARE.
|
||||
|
||||
Marine safety functions implemented herein follow the spirit of IEC
|
||||
60092-504, IACS UR E22, ABYC E-11, NMEA 2000, SAE J1939, and IMO
|
||||
MARPOL/SOLAS, but formal certification of compliance is the responsibility
|
||||
of the vessel operator and the certifying authority of jurisdiction.
|
||||
Reference in New Issue
Block a user