A permanent audit reconstruction must preserve evidence without inventing certainty.
The customer needs a complete compliance record, while security needs every reconstructed event to show its provenance.
Who you’d be doing this for
“Compliance asked for the policy history, and I had to tell them 43 changes aren’t in the export.”
Sven Andersson · Director of Engineering Operations
Prepares audit evidence for a healthcare organization using centrally governed developer tools.
What is at stake
A six-hour replay omitted at least 43 policy-change events from a healthcare customer’s audit export. You must weigh a complete record against the risk of certifying evidence that cannot be fully observed.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- completeness vs evidentiary certainty
- customer deadline vs signed review
- recovery throughput vs live ingestion safety
- external evidence vs product audit ownership
Why Cursor
Cursor audit logs support enterprise controls around models, MCPs, Tools, and network restrictions that regulated customers must be able to evidence.
Written with these in mind
Not your kind of problem? 42 more at Cursor, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.