OBTUSE AIBook a call
Build
Products
Proof
Studio
Book a call
OBTUSE WORK / PORTABILITY CONTRACT

Your exit is a feature, not a negotiation.

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. Version 0.37 also preserves named-member roles and access receipts in full-fidelity recovery while redacting derived credential hashes from readable exports. Its Migration Center previews and validates imported rows before they join the operating record. It creates a password-encrypted recovery file for protected off-device storage and manual transfer. Portability is implemented in the public preview—not reserved for a future tier.

Discuss a private pilotReturn to Obtuse Work
THE PROMISE

You can leave with the operating record. Credentials remain protected. Recovery remains deliberate.

01 / THE EXPORT PACKAGE

Readable now. Recoverable later.

  • One human-readable JSON document with the export format, schema version, table definitions, table count, row count, and all durable rows
  • One standards-readable CSV for every durable application table
  • One integrity-checked SQLite recovery database for full-fidelity restore
  • One password-encrypted .obtuse-work recovery file for protected storage or manual transfer to another Windows computer
  • Readable JSON and CSV exports with derived Team Authority credential hashes explicitly redacted
02 / WHAT TRAVELS

The operation, not a summary.

  • Customers, leads, messages, tasks, appointments, and workspace items
  • Appointment reminder artifacts, consent basis, exact-version bindings, message and artifact hashes, and observed-delivery receipts
  • Communication sessions, consent state, ordered transcript turns, routing decisions, human-handoff reasons, adapter manifests, fixed-suite qualification runs and case results, retention previews, and non-content deletion receipts
  • Reusable line-item presets, quotes, invoices, document lines, delivery packets, artifact hashes, response receipts, encrypted-exchange profiles, contract and live qualification results, hosted lifecycle receipts, checkout evidence, and the money ledger
  • Approvals, operating events, cost records, saved report views, and webhook delivery receipts
  • Knowledge, sources, memory relations, contradictions, settings, and operator conversations
  • Named workspace members, roles, lifecycle state, and durable access receipts
03 / WHAT STAYS PROTECTED

Portable data without portable secrets.

  • Credential Manager secrets are excluded
  • Derived member credential hashes are redacted from readable exports
  • Encrypted transfer uses Argon2id and XChaCha20-Poly1305
  • 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 encrypted path authenticates its password, metadata, and content before SQLite validation. Every recovery path checks structure and integrity before changing the active workspace, then keeps a safety copy of what it replaced.

01

Authenticate every byte

Argon2id hardens the recovery password, while XChaCha20-Poly1305 authenticates the exact recovery metadata and workspace before restore. Team Authority uses a separate Argon2id derivation for each member passphrase.

02

Schema before replacement

A selected recovery database must match the current schema or a known additive predecessor before it can replace the workspace.

03

Safety copy before restore

The current database is copied before replacement, and the incoming database must pass SQLite integrity checks.

04

Secrets stay separate

API keys, exchange credentials, and signing secrets remain in Windows Credential Manager. Readable exports also redact derived member credential hashes; full-fidelity recovery preserves the protected local access state.

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.

Discuss Obtuse WorkExplore the workspace