WKTRA Lab / Product research
Small tools for specific engineering friction.
WKTRA Lab validates focused software ideas before making product claims. Every track begins with workflow evidence, a narrow boundary, and human approval at the important decisions.
Research principle
Evidence first. Automation only where it earns trust.
The aim is not to build a broad engineering platform. The aim is to understand one costly failure mode, test the smallest useful workflow, and keep technical responsibility with the engineer.
01Problem validation
Engineering Release Pack Assistant
The friction
Engineering handovers can fail for simple but costly reasons: the wrong revision, an incomplete document set, inconsistent identifiers, or a release package whose contents are difficult to verify.
Validation direction
Validate a narrow, human-reviewed assistant that checks release-pack structure, document presence, revision consistency, and traceability before handover.
Questions being tested
- Which release checks repeat across real engineering teams?
- What evidence should accompany every flag or recommendation?
- Where must the responsible engineer remain the final decision-maker?
Boundary
The first version will not judge geometry, detect missing dimensions, certify compliance, or replace formal engineering approval.
02Held for phase two
Onshape VariantBuilder
The friction
Approved product variants often repeat the same configuration logic while engineers manually rebuild features, naming, metadata, and release steps.
Validation direction
Explore a controlled Onshape workflow that applies approved variant rules while keeping exceptions visible and editable by the engineer.
Questions being tested
- Which variant rules are stable enough to encode?
- How should an engineer review exceptions before release?
- Which narrow family of parts would make a credible first pilot?
Boundary
This remains a follow-on concept until the first research track produces useful evidence and a clearly bounded workflow.
Research conversations
Does your release process expose the same friction?
WKTRA is interested in grounded conversations with engineers and technical managers who can describe the current review process, its failure modes, and what a trustworthy first tool must never do.
Share a workflow problemStart a conversation
A useful product begins with a specific failure mode.
Share an example of a release-pack gap or repetitive check that is worth understanding.
Discuss your goals