🎯 Objective

The primary goal of this milestone is to graduate Plesty from individual repository prototyping into a functionally synchronized ecosystem where users can independently set up HUB modules and run experiments. By completion, we will achieve our first end-to-end integration loop: executing a non-production experimental demo that commands a target physical or simulated device, backed by rigorous automated data-layer and compliance checks.

🚀 Expected Outcomes

• Core Abstractions: Finalize Abstract Base Classes (ABCs) for Devices (and possibly Experiments) in plesty-lib
• Data Layer: Define core schemas in plesty-lib to enforce unified data/metadata and standardized physical units. Provide tools for storing data in a unified (hdf5?) format.
• Developer Tooling & Automation: Update the plesty-sdk and plesty-ci to validate namespace compliance, semantic versioning, licensing, safety clamps, and dependency coexistence.
• Ecosystem Inspiration: Deliver a standalone experimental demo sequence to serve as a design blueprint for future, formalized Experiment HUB modules.
• First HUB Ecosystem Implementations: Develop the initial functional device drivers using streamlined templates.
• UX & Documentation Upgrade: Improve user experience by improving website&documentation. Separate content from functionality in the plesty-website repo.

🛑 Definition of Done

• Core Architecture: Base classes for Devices (and possibly Experiments ) are defined, documented, and fully integrated with the new data layer.
• Tooling & CI: The plesty check validation engine runs successfully both locally and in the remote plesty-ci pipelines, automatically posting evaluation reports directly as Merge Request (MR) comments.
• HUB Validation: All hub modules are compliant to the plesty-ci
• Interoperability: At least one pilot device module can be initialized via the CLI, satisfies all plesty-ci rules , and maps correctly to conflict-free dependency ranges.
• Integration Demo: A target experimental demo sequence successfully executes a seamless command and measurement loop with the pilot device (physical or simulated).
• Docs & Governance: The project website is decoupled from code logic, onboarding materials are updated to reflect the new validation rules, and all sprint-related technical debt is explicitly logged as tracked GitLab issues.