From Pixels to Club Physics: An Evidence-Bounded Architecture for Monocular Golf-Club Pose, Kinematics, and Training Data
What a phone camera can tell us about a golf club—and where physical measurement needs more evidence.
Methods, experiments, and technical reviews. Read the findings alongside their assumptions, evidence, and limitations.
What a phone camera can tell us about a golf club—and where physical measurement needs more evidence.
Three sign-recognition models recovered when the training recipe changed. A closer look at what model comparisons actually measure.
An audit of sign recognition on unseen signers, with multiple seeds and explicit limits on what the results establish.
Why one average accuracy score can conceal very different experiences across 21 signers.
Real-time scoring of physical-object sports requires a computer vision pipeline that can simultaneously satisfy constraints from three domains: inference latency (sub-35ms end-to-end), detection reliability (>99% on custom domain data), and commercial licensing (Apache 2.0 for network-service deployments).
Generic computer vision model fine-tuning treats dataset construction as secondary to architecture selection.
Selecting the right Claude model tier for a given artifact type is the single highest-impact cost decision an operator makes in an agent-mediated workflow.
TPL-2026-005 established that sprint-contract discipline reduces overrun rates in solo-operator agent-mediated work (median overrun 78% → 12%).
Long agent sessions (those exceeding two hours of continuous operation) accumulate a characteristic failure pattern we term brief-drift: the gradual divergence of agent behavior from its original operator-specified constraints, without any single identifiable failure event.
We report a case study (n=1 task, three agent harnesses, single operator) comparing Claude Code, OpenAI Codex CLI, and Cursor on the construction of a multi-stage computer-vision evaluation pipeline.
Computer vision systems shipped to production frequently report misleading evaluation metrics due to undetected overlap between training and held-out eval data.
Modern long-context language models (1M-token windows) make it tempting to load an entire reference corpus and draft against it; the implicit premise is that more context is always better when accuracy matters.
Operators increasingly compose work as a chain of specialized LLM agents: a routing agent dispatches to a planning agent which delegates to a coding agent which calls a review agent.
Real-time computer vision systems that must operate under latency constraints face a tension between detection accuracy and inference speed.
Parley is an AR-glasses product for bidirectional deaf/hearing conversation; the research arm is in Phase-0/1 Kaggle-published exploration and the consumer hardware (Everysight Maverick AI) has not yet shipped.
LLM-assisted provisional patent drafting promises faster cycle time at the inventor-startup phase, but the question for operators is how much of the LLM draft survives attorney review.
Plan mode, the agent-harness convention of producing and approving a written implementation plan before any code is written, is widely advocated as a discipline for non-trivial coding work, but its quantitative effect on time-to-merge has rarely been measured outside anecdote.
Blameless postmortems are widely advocated as a structural-learning discipline, but their effectiveness depends on whether action items reach the mechanical layer (gates, hooks, contract criteria) rather than remaining as discipline-only commitments.
Pre-launch entertainment-venue site searches are constrained by an unusual cocktail of filters: zoning compatibility, square-footage and ceiling-height fit, ABC-license geography (in NC, alcohol licensing depends on municipal jurisdiction and proximity to schools/churches), and proximity to demand.
Solo operators running agent-mediated engineering work routinely overrun sprint estimates by 50-200% of the originally scoped time.
Sub-agent invocation (spawning a child agent to handle a bounded subtask) is increasingly common in solo-operator AI workflows, yet the conditions under which it produces a net benefit remain poorly characterized.
Operators running agent-mediated engineering workflows routinely lack visibility into the per-artifact token cost of shipped work, treating the monthly API bill as a single aggregate figure.