🎯 Objective

Consolidate Plesty into a scalable, low-friction, user-centred ecosystem. — the missing pieces of a plesty MVP that give users a strong incentive to adopt it: broad device coverage on stable, versioned foundations, a device verification standard, and documentation that people who don't code much can follow. This milestone focuses on minimizing adoption friction across two core fronts:

1. For Users (especially non-expert coders): Enabling seamless lab workflows—from knowing which devices exist and booking them via plesty-manager, to clear Python access instructions, available experiment scripts, and linked measurement documentation and data.
2. For Developers: Making code sharing and HUB integration effortless at any maturity stage through high CLI verbosity (plesty-sdk), standardized module structures, and step-by-step contributor guides.

🚀 Expected Outcomes

Priority Outcomes

1. Broad HUB Device & Module Coverage:
   • Legacy Migrations: Migrate legacy modules (e.g. pyforpicam, picamccd, spectrapro_hrs, lightfield_spectrometer, analyzers/positionestimate) to the Quantum Standard. Published: plesty-pyforpicam 0.5.0 (PyPI, 2026-09-10).
   • Core Optical Hardware: Finalize and publish plesty-spectrometer as the critical foundational driver for optical measurement pipelines.
   • Setup Ports: Support setup responsibles in porting new devices from plexy using the contributor tutorial. Field-test every module end-to-end on real hardware (following process #17 (closed)).
2. Device API Testing & Verification Standard:
   • Redesign the device-API test pipeline into a standard verification suite (mock tier for local CI, hardware tier for field tests) and enforce it via plesty check and plesty-ci. In Addition, make sure testing on actual hardware is as fast as possible.
3. User Experience, Documentation & Frictionless Code Sharing:
   • Portals: Adapt/Launch Quickstart and landing pages for Users and Developers on plesty.net.
   • Developer Onboarding: Improve website and documentation UX, create tutorials and maximize CLI verbosity (plesty-sdk) to guide developers step-by-step when contributing or publishing code at any maturity level.
   • Feedback: Implement workflows for simple reporting of bugs and feature requests by users.
4. Stable, Versioned Foundations:
   • Release the plesty-lib / plesty-sdk v0.3 line with backwards-compatibility guarantees for patch releases, a documented deprecation policy, and version-differentiated documentation.

Supporting & Platform Work

• a. CI Evaluation Reports: plesty-ci automatically posts plesty check evaluation reports directly as Merge Request (MR) comments.
• b. Analyzers & Monitors Architecture & Alignment:
  • Draft the Analyzer base class in plesty-lib for client-side data reduction and discuss/review requirements and architecture with the PO. Test with positionestimate analyzer.
  • Draft the Monitor base class in plesty-lib for data visualization and discuss/review requirements and architecture with the PO. Create a monitor for spectra visualization.
• c. General plesty-manager Rollout (manager.plesty.net): Deploy a functional management interface that enables lab users to:
  • See which devices are available and book them.
  • Know exactly how to access these devices via Python when they want to run their experiments.
  • Discover available experiment scripts and where/how to run them.
  • Access direct links to measurement documentation and generated dataset files.
• d. Target Integration Experiment:
  • Execute an Automated Statistical Spectroscopy Experiment: PL imaging \rightarrow Quantum Dot (QD) positioning --> automated stage movement to QD --> spectrum acquisition --> repeat for many QDs --> analysis and visualization.
• e. AI-Assisted Development (Discussion Item): Formulate and record the agreed approach for AI agents/skills that generate or port device APIs from plexy.

🛑 Definition of Done

• Critical Hardware & Modules: plesty-spectrometer is fully implemented, published, and Quantum-Standard compliant; all HUB modules comply with the Quantum Standard (or are archived to sandbox); at least 3 new device modules are ported from plexy and field-tested on physical hardware.
• Architecture Governance: Analyzer and Monitor base classes are reviewed and agreed upon with the PO, then locked and documented in plesty-lib.
• Verification Standard: The device-API verification suite ships in plesty-lib and runs as a mandatory plesty check / CI gate.
• Foundation Stability: plesty-lib and plesty-sdk v0.3 released with an explicit backwards-compatibility and deprecation policy; no breaking change lands without a version bump.
• UX & Code Sharing: plesty.net landing pages are live; documentation/website follows a unified structure and design; plesty-sdk provides verbose feedback during scaffolding and verification; user feedback templates are integrated.
• CI Feedback: All MRs in HUB and core repositories receive automated verification report comments from plesty-ci.
• Lab Manager Portal: manager.plesty.net is live, displaying device availability, booking options, clear Python access snippets, experiment script locations, and links to documentation and data.
• Statistical Spectroscopy Integration: The Automated Statistical Spectroscopy experiment (PL imaging \rightarrow QD positioning \rightarrow movement \rightarrow spectrum \rightarrow analysis/visualization) executes end-to-end.
• AI Governance: Decision on AI-assisted device development is recorded as a tracked GitLab issue before implementation begins.