ArrowDNA ProLab™
Measured bow-shop intelligence for tuning, repeatability, calibration, and customer-ready documentation.
ProLab V1 system status
This V1 gate verifies the accepted engine chain, required operator controls, and compatibility of existing device-local records. Shop Pilot permission is a separate server-controlled access layer and does not change the measurement engines.
One clear next action
ProLab reads the current session and shows what is supported, what is limited, what is optional, and what should happen next. Advanced steps add evidence but do not silently become requirements for Final Spec finalization.
Advanced / optional evidence
Workflow status reflects evidence presence and supported analysis state only. It is not a quality score, tune score, pass/fail certification, or hidden completion requirement.
Customer, bow & instrument identity
Instrument provenance + check context
Record the exact instrument used and, when available, the date and reference for its most recent shop check or calibration. ProLab does not invent accuracy, certification, or expiration intervals.
Keep every session tied to the right system
History is built from the saved sessions and Final Specs already on this device. ProLab groups exact customer identity and keeps serialized bows separate from name-only bows so it does not silently merge records that only look similar.
A bow without a serial is a name-only identity group. Add a serial when available if you need physical-bow continuity. Incomplete records remain unassigned rather than being guessed into a customer or bow.
Draw-board truth
Draw-force curve / stored energy
Enter measured draw distance in inches, force in pounds. One pair per line. Use at least 3 points and keep the same distance reference through the series. The first measured point must be 0.00 in at your chosen starting reference so ProLab does not label a partial curve as stored energy.
Repeatability, not a single lucky shot
Enter measured fps values separated by commas, spaces, or new lines. ProLab reports average, extreme spread, and sample standard deviation.
Fit this arrow’s effective drag from real velocity loss
Enter one measured reading per line as distance yd, speed fps. Include a launch series at exactly 0 yd plus measurements at at least two distinct downrange distances. Repeat a distance on multiple lines to record multiple shots there.
This is a system-specific fitted effective drag β using ArrowDNA’s accepted RK4 quadratic-drag solver. It is not a direct Cd measurement and should not be transferred to a different arrow configuration without verification.
Know how stable the measurements are
ProLab uses the chronograph and downrange readings already entered above. It reports observed shot-to-shot variation and evidence coverage without creating a hidden quality score or universal pass/fail threshold.
The descriptive ±2 SD band is not a confidence interval or equipment tolerance. Instrument calibration age is shown only when both dates are recorded; ProLab does not invent an expiration limit.
Match the set with measured spread
One arrow per line: weight gr, spine deflection in, balance point in, arrow length in. Leave an unavailable field blank.
Matched-set criteria
You define the shop tolerances. Leave a field blank to exclude that measurement from matching. ProLab applies no hidden default tolerances and no weighted quality score.
Fit your bow instead of borrowing somebody else’s model
Use at least three measured finished arrow weight, measured speed pairs from this bow. A wider useful weight span improves the fit's ability to describe the bow.
See exactly what changed
Compare two saved ProLab sessions. ProLab recomputes both sides from their original measurements, then reports Baseline → Comparison → Delta. Increase/decrease is descriptive only—there is no hidden tune score and no automatic winner.
If customer or bow identity differs, ProLab shows an identity warning rather than silently treating the records as the same system.
One bench session, one auditable record
Freeze what was approved
Finalization creates a separate, frozen device-local snapshot of the current session. Later edits do not change the finalized record. If you finalize again, ProLab creates a new revision instead of overwriting the earlier customer handoff.
Final Specs are Founder-preview records stored on this device only. Finalization does not convert an OPEN evidence block into verified truth and does not sync to Supabase in 90.4.10.
90.4 Foundation stores Founder preview sessions on this device only. Account-synced shop/customer storage is intentionally held for a separate RLS migration and entitlement decision.
Move ProLab data without losing frozen history
Export the device-local ProLab working sessions and Final Specs into one versioned JSON backup. Import always validates the file and shows a preview before any local data changes.
Import / restore a backup
Replace all local ProLab data from this backup
This replaces the current device-local working-session and Final Spec stores with the validated backup. It does not change server data. Type REPLACE to authorize it.
Backup files can contain customer, bow, measurement, and Final Spec information. Store them appropriately. SHA-256 verifies file integrity only; it is not a digital signature and does not prove who created the backup.
ProLab records measurements that professional tuning equipment can produce—draw-board geometry, peak/holding weight, let-off, chronograph series, arrow mass and static-spine deflection—then separates those measurements from calculated and modeled outputs.