Core research systemTwo-pass governed flow
Product status · Updated August 8, 2026
Truthful status, not a green-light decoration.
This page separates what is operational, what has boundaries, what is being improved, and what actually changed. It is a product-readiness record—not a claim that outside AI providers never fail.
Research custodyDevice first
Encrypted BYOK10 providers
Recovery + free capacityActive improvement
01
Working now
Built, connected, and available—not merely planned.
Exact two-pass DMap workflow
Three independent Round 1 responses are followed by an automatic Disagreement Map. The user can preserve evidence or run one DMap-informed Round 2. Final synthesis is explicit and human ratification remains separate.
Device-first research custody
Archives, DMaps, Round 2 movement evidence, receipts, local ledger cache, and new accepted source originals are stored in the browser-managed device vault first. Cloud backup is optional.
Ten-provider BYOK catalog
OpenAI, Anthropic, Google Gemini, Ollama Cloud, Groq, Mistral, DeepSeek, xAI Grok, Perplexity, and Cohere can be connected to a workspace with encrypted server-side key custody.
Free account services without cloud-storage lock-in
A free account can use approved shared free-model inference, three BYOK connections, teams, and optional cloud backup. Device-local research storage does not require a paid plan.
Portable receipts and archives
Research workspaces and decision receipts can be exported. Compatible exports can be reopened, saved evidence can reopen its pipeline, and append-only history remains inspectable.
One Complete membership
Monthly or annual ChatVaultAI Complete unlocks both ChatVaultAI and ChatCatharsis through one subscription and one billing portal.
02
Known limitations
Boundaries to understand before relying on the system.
Device storage is still browser-managed
Clearing site data, resetting a browser profile, or losing a device can remove local research. Request persistent storage when available and export important work. Optional cloud backup provides another recovery path.
Live generation still leaves the device
A live council sends the relevant prompt and instructions to the declared provider, and comparison material to the declared compiler. Device-first custody does not make third-party inference local.
Live generation needs provider access
A live council requires approved shared capacity or a valid connected provider key. Simulation remains available when live capacity or a provider is unavailable.
Provider health is external
Model availability, rate limits, latency, and vendor policy can change outside ChatCatharsis. The execution receipt records what provider and model actually resolved.
Original-file intake is bounded
New accepted originals are device-first, require explicit transfer and supported handling, and remain subject to the current 5 MB intake limit. Cloud copying occurs only when optional backup is enabled.
03
Improving now
Current directions, without invented release dates.
Device-vault recovery testing
Expanding migration, persistent-storage, quota, export, restore, site-data-loss, and multi-device backup tests around the new device-first boundary.
Free-user capacity
Keeping core custody and governed research free while using shared free-model capacity, BYOK, fair-use protection, and optional backup to avoid turning infrastructure cost into an artificial research barrier.
Provider evidence
Designing truthful provider health and benchmarking reports that distinguish measured results from marketing claims and avoid pretending one model is always best.
Private support intake
A privacy-safe problem-report path is planned so users can send reproducible steps without exposing private research, credentials, or payment data.
04
Release record
Dated user-visible changes that reached production.
Device-first research custody
Moved the research body to IndexedDB-based device storage, added persistent-storage and quota visibility, optional cloud backup, device-first source originals, local ledger caching, and smaller digest-oriented cloud ledger payloads.
Two-pass Disagreement Map flow hardened
Added exact three-choice Round 1 behavior, same-DMap Round 2 isolation, required held/revised/resolved/still-disputed/uncertain movement evidence, explicit synthesis, human ratification, and saved-run return paths.
Encrypted BYOK expanded from three providers to ten
Added a searchable provider catalog, provider-specific adapters and verification, Compiler and Expert Council selection, and Free-versus-Complete connection policy.
Team workspaces reached production
Added workspace creation and switching, verified-email invitations, owner/editor/viewer roles, and server-only audit custody.
Prepare a useful problem report
Until private support intake is published, preserve the page address, approximate time, exact steps, expected result, observed result, browser and device, and non-sensitive error text or screenshot. That turns “it broke” into evidence that can be reproduced and fixed.
Never include passwords, account tokens, provider keys, payment information, or private research content. Security concerns and account-specific details should not be posted publicly.