Obtuse Work keeps the operating record on your machine and gives the whole durable workspace back in formats you can inspect, move, archive, or restore. Portability is implemented in the private-pilot build—not reserved for a future tier.
Knowledge, sources, memory relations, contradictions, settings, and operator conversations
03 / WHAT STAYS PROTECTED
Portable data without portable secrets.
Credential Manager secrets are excluded
Consequential restore stays confirmation-gated
Local rotating backups remain available between exports
GUARDED RECOVERY
Restore is powerful. So it is deliberately hard to do by accident.
The recovery path validates structure and integrity before it changes the active workspace, then keeps a safety copy of what it replaced.
01
Schema before replacement
A selected recovery database must match the current schema or a known additive predecessor before it can replace the workspace.
02
Safety copy before restore
The current database is copied before replacement, and the incoming database must pass SQLite integrity checks.
03
Secrets stay separate
API keys and signing secrets remain in Windows Credential Manager. They are not written into exports or outbound event payloads.
OPEN EVENT RAIL
Your data can move before you do.
A provider-neutral outbound webhook can send newly created operating events to your HTTPS receiver. Each delivery is HMAC-SHA256 signed, uses a stable delivery identifier, records a receipt, and advances only after receiver success.
Own the workflow. Own the record. Keep the option to leave.
The current private-pilot build includes the portability foundation described here.