Point Designs Partial-Hand Workflow — Scope Map (v0.2)

A stage-by-stage decomposition of the Point Designs partial-hand workflow, mapped to the Spentys building blocks that deliver each step. Shared for the scope walkthrough.

§ 00 · How to read this map

Each phase contains parent stages; each stage decomposes into child sub-processes. Every sub-process is described across four layers — what the user does, what the system computes, what data moves through (in → out), and which Spentys module owns it. The module column is a draft assignment (“draft — confirm” = best-guess, to confirm at the walkthrough); the status tag flags whether that module exists today, needs adapting, or is net-new build.

Note the S1 fork: a mold scan with liner skips S2 and S3 entirely and enters at S4, because the liner volume is already present on the scan.

Phase mapping vs discovery. Discovery framed a four-stage roadmap (Phase 1, 1.5, 2, 3); this map and proposal v0.5 consolidate to two delivered phases — discovery’s Phase 1.5 (alignment-transfer replication) is absorbed into Phase 2 (S8a, the physical-aligner-scan path), and Phase 3 (full automation) is the unpriced future-perspective track. The two-phase framing is a deliberate consolidation, not a scope reduction.

Legend. Status — Existing (reusable as-is) · Adapt (existing module, modified) · New build (net-new). Module — Confirmed vs Draft — to confirm. Data — in → (input) · → out (output).

Phase 1 — Diagnostic Device Workflow

Months 0–6 · internal MVP. Flow: S1 Import scan → S2 Modify (mold path) → S3 Liner volume → S4 Build frame → S5 Export → S6 OMS connection.

S1 · Import scan

Ingest the case — two scan types, and the fork that follows from them.

The fork starts here. A mold scan takes the full path: S2 modify → S3 liner volume → S4 frame. A mold scan with liner skips S2 and S3 — the liner volume is already physically present on the scan — and enters directly at S4, where only the attachment points need defining.

S2 · Modify

Guided, region-based modification — replaces the physical plaster-modification step.

Only runs on the mold-scan path. A mold-scan-with-liner skips this stage. This is the guided workflow: rather than separate reduce / smooth / raise tools, the editor walks the user region by region — each region is enclosed by a trimline and carries a region-specific automated edit, with granular control exposed for tuning.

S3 · Liner volume

Define the liner extent and generate the liner volume placeholder.

The liner is a volumetric placeholder — design specifics come in a later stage (S7). The zipper (closure for the liner) is defined here; the strap (closure for the frame) comes in S4. A mold-scan-with-liner skips this stage: its liner volume is already on the scan.

S4 · Build frame

Generate the frame on top of the liner volume — the diagnostic device.

Both paths meet here. The frame sits on top of the liner volume — like a socket over a liner. A mold-scan-with-liner enters directly: its liner volume is the scan itself, so it needs only attachment points defined. The frame carries the strap (the zipper belongs to the liner, S3). The frame device is the Phase 1 output.

S5 · Export

Produce manufacturing-ready geometry for the diagnostic device.

Output: PA12 rigid frame, STL / print-ready geometry — the Phase-1 diagnostic-device output.

S6 · OMS connection

Write the design output back into the order record.

Closes the Phase 1 loop: the design output becomes part of the OMS order. Web editor lives inside the OMS; visibility in the order form itself is configurable.

Phase 2 — Definitive Device & Alignment

Months 6–12 · customer-facing. Flow: S7 Build liner device → S8 Finger placement → S9 Align + compute → S10 Definitive output.

S7 · Build liner device

Same logic as S3 — but generates the actual liner device, not a placeholder volume.

S7 reuses the S3 region logic, but instead of a placeholder volume it generates the actual liner device geometry. It runs only on the hand-scan path — a hand-scan-with-liner already carries the liner shape and skips straight to S9. The computed S7 model and the hand-scan-with-liner both land in S9. This is where the printable (TPU) liner is produced — its material and closure are confirmed by PD before this stage (the Phase-1 frame is PA12; see S5 and the 2026-06-04 material decision).

S8 · Finger placement

Establish finger positions — from a physical-aligner scan, or from manual landmarks.

S8 has two entry doors, both converging into S9. S8a — the client physically places aligners on the printed model and scans it; the algorithm recognises the aligners and uses them as placement identifiers. S8b — no physical fitting; the client places landmarks on the liner where fingers go, at a set orientation. Fingers are a low-resolution representation of the PD fingers — PD delivers the geometry, Spentys decimates it for fast realtime alignment. The low-mesh fingers still carry the data needed for the adapter-fit calculations.

PD answer (2026-06-04, Q1). The current arrow alignment is done through Freeform’s built-in “registration” feature (auto-aligns known geometries) and is likely locked inside Freeform. PD has confirmed a different marker system (e.g. QR-style) is acceptable — so 8a.2 can build a simpler, more detectable marker rather than reverse-engineering the arrows. This softens the script-reuse dependency on PD.

S9 · Align + compute model

Finetune finger alignment, then compute the printable definitive model.

Both S8 entry doors converge here. The rescanned arrow-scan is fitted onto the original designed scan — the new scan is the working surface, the original is fitted to it (avoids redoing work). In Phase 2 the rescan drives finger-alignment transfer only, plus manual trimline re-projection: because the practitioner may have manually trimmed the socket or liner, trim lines are re-projected onto the new mesh and, if they have moved, the user nudges them manually (no automatic re-cutting in year one). Once fitted, the user can show/hide the rescan to adjust trim lines, then gets movement control — fingers slide along the diagnostic surface to finetune the fitted position. The final step computes the model — booleans, build-ups, added geometry — into a printable 3D file, on the existing geometric backend.

PD answer (2026-06-04, Q5) — scope boundary [monitor closely]. PD confirmed the rescan is not purely an alignment transfer: in some cases trimline and volume changes are physically made to the diagnostic before scanning, and more often changes are requested but not implemented (noted as drawings on the diagnostic or in the returned diagnostic checklist) and applied when the definitive socket is made. Decision (Michael, 2026-06-04): Phase 2 handles finger-alignment transfer and manual trimline nudging only; rescan-driven volume changes / socket re-modification are explicitly out of scope for this engagement and pushed to a future phase after Phase 2. This is the most likely Phase-2 scope-creep vector and needs close monitoring.

S10 · Definitive output

Validate components in the OMS and close the order.

Closes the definitive-device loop inside the OMS — all output files loaded and rendered in 3D for a clear review before the order is closed.

Point Designs partial-hand workflow — scope map v0.2. Pairs with proposal v0.5 §03.