Cursor deleted it. The trace survived.

Contenox ran a 41-step plan and rewrote this site's copy autonomously — reasoning stored step by step in a local SQLite file on this machine. Then Cursor, the cloud-backed AI editor, deleted the enterprise directory instead of making a .gitignore entry.

We recovered everything. Not from a cloud backup. Not from a pushed branch. From the audit trail Contenox left in .contenox/local.db — the full goal, the copywriter brief, the step summaries, the reasoning chain.

$ contenox plan show
Plan: plan-35e3bf43 (active) — 22/41 complete
Full goal, step summaries, reasoning chain. Still there.

$ git log --oneline
04d0888 Try to fix the admin area
One commit. The damage Cursor left behind.

That's the difference between a tool that executes on your side and one that executes on someone else's.

When Cursor acts, it acts in the cloud — or at least with no persistent local record of what it intended. When Contenox acts, every step is written locally before it runs. The plan is yours. The trace is yours. The recovery is yours.

No one else's uptime. No one else's audit log. Your machine, your record.