Problem
Biomedical cell-location work can lose position context when microscope capture, embedding, trimming, and data export live in separate tools.
My role
I built the public-safe explanation from the PRD, software manual, local source metadata, and reviewed prototype screenshots while keeping source code and operational details private.
Constraints
The public boundary excludes source code, private infrastructure, credentials, client or employer details, internal data, and proprietary operating records.
Key decisions
The public page uses only a static overview and sanitized screenshots: enough to show the workflow, not enough to publish clone, API, download, credentials, internal addresses, customer data, or proprietary operating records.
Architecture
The verified local stack is a web UI plus Python FastAPI backend: the manual describes HTTP REST and WebSocket communication, a hardware abstraction layer for Moonraker and RS485 devices, and file-based JSON/image session storage.
Engineering evidence
Evidence used here is limited to the latest local README/PRD-derived material, the June 2026 software manual/PDF, local package metadata, and three reviewed screenshots from the coordinate, embedding, and session-export flows.
Result
CWC now has a durable public entry that communicates its place in the project set without exposing private material.
Limits & next steps
This page intentionally does not claim private metrics, customers, deployment addresses, source access, or implementation details that are not approved for publication.


