# mk5-electronics
Santiago
Custom IMU board still worth it? Noise floor looks fine on the COTS unit after VQF.
Zaid
Agreed. Custom adds ~6 weeks for no measurable gain. Leaning COTS.
Julian
+1. Ship Mk5 on the off-the-shelf part.
Screenshot it. Search it later. Everything stays on your machine.
your team makes decisions every day across slack, email, calls, and jira. three months later someone asks "why did we do it that way" and nobody remembers. retrace does. hit a hotkey, screenshot the conversation, and the reasoning gets extracted and stored on your machine. one search to find the why, months later. private, local, yours.
Click through to see the whole workflow.
Capture anything on your screen. Slack, email, Jira, whiteboard, terminal.
No cloud. No API tokens. No connectors. No background recording. You choose what to capture, screenshot by screenshot. That's what makes RETRACE safe for ITAR, ISO 13485, and audit-heavy teams.
RETRACE captures the reasoning behind decisions from screenshots of any tool on your screen, then makes that history searchable in one keystroke. Everything runs locally on your machine.
Hit a global hotkey from anywhere. RETRACE screenshots what's on your screen, reads it with AI, and extracts a what and a why. It classifies the record as a Decision, Learning, Task, or Note. You review what the AI proposed, confirm or edit the fields, and it's saved.
Anything on your screen. Slack threads, emails, Confluence pages, Jira tickets, whiteboard photos, video calls, terminal output, oscilloscope screenshots, PDFs. If you can see it, RETRACE can read it.
No. Everything stays on your device. There are no API connections, no OAuth tokens, no background recording, no data leaving your machine. You choose what to capture, one screenshot at a time.
When RETRACE extracts a record, each field — the what and the why — is marked as confirmed (a human verified it), suggested (the AI proposed it and you haven't reviewed it yet), or empty (not enough context to extract). You always know what came from the AI versus what a person locked in.
Hardware engineering teams, regulated industries (ITAR, ISO 13485, functional safety), and anyone who needs to trace back to why a decision was made months after the fact. Especially teams where decisions happen across many tools and the reasoning never gets written down.
From our design partners
We walked back a design decision over a constraint nobody had written down. By the time it surfaced, the reasoning behind the original call was already gone.
I run a three and a half hour meeting every week just to chase what people committed to and never closed. The moment I was travelling, decisions got dropped.
Request access for your team today.