Meeting: Manual Interventions in Automation & Open Items¶
Date: February 17, 2026
Duration: 33 mins
Partner: Kach Motors
Meeting Summary¶
What are "manual interventions"? @ 3:30¶
The team talked through what it really means to jump in and change things manually. A few key takeaways: - We still need a person to step in when dimensions or material grades change, or for specific settings that shift the manufacturing process. - Freedom to override: The system shouldn't be a black box; users should be able to nudge the recommendations. - Getting smarter over time: We want to record these changes so the system learns from them, eventually needing fewer manual tweaks.
Should we explain every change? @ 9:03¶
We debated how much a user should have to explain when they override something: - Traceability matters: We definitely need notes on "key fields" so we know why a decision was made. - Don't make it a chore: We want to avoid forcing explanations for every tiny detail—that just slows people down. - Successive improvement: The goal is to see fewer overrides each time we quote the same part.
Prototypes and Samples @ 18:20¶
How do prototypes fit into the cost? - Validating the design: For new customers or unique parts, a prototype is non-negotiable to prove out the process. - Refining the numbers: We usually start with a cost based on something similar, then use the prototype run to fix the final numbers. - Flexible states: The system needs to handle both "Draft" costs (before a prototype) and "Final" costs (after the sample is validated).
Managing change over time @ 25:28¶
How do we handle shifting material prices or better shop floor processes? - Keep a history: We need to be able to look back at old versions and understand where they came from. - The "Why" behind the change: Traceability is huge for understanding final cost adjustments. - An assistant, not a replacement: We're positioning this as a tool to save effort, not a 100% "push-button" automation, especially at first.
Action Items¶
- Document Discussion: Document requirements for team review (Preetam).
- Requirements Breakdown: Categorize as "Must-haves" vs "Nice-to-haves" for MVP.
- Effort Estimation: Provide development estimates based on documented requirements.