Your record. Your sources. Your assistant.
Capabilities and source coverage
Pref maintains a factual investment record through your own assistant. Muse is the existing private pilot setup path. The shared HTTP backend preserves the same investor's records across authorized clients. Claude Google sign-in and synthetic save/read have been verified for the approved owner. Other assistant paths have prepared adapters, but need their own configuration and actual installation checks. Public enrollment remains closed.
What the earlier private pilot demonstrated
The hosted private service stores source-backed holdings and owner records, preserves observation history and supports fresh-conversation retrieval. On-demand Muse source collection, save and retrieval, selected acknowledgement and a quiet repeat have passed in the existing pilot. The API also supports source coverage, reversible document assignments, correction history and CSV export.
These are factual records and references, not an independent reconciliation of ownership, current balances or completeness. Corrections append history. Conflicting and missing facts remain visible; a reported zero is different from an unknown value. Showing a capital call does not prove payment or completion.
What may be saved
Concise holding and ownership facts, sourced financial facts, brief factual summaries, document references and collector-supplied content hashes. The prepared release also saves owner-confirmed structured monitoring/source preferences with confirmation provenance. The record also contains observation timestamps and IDs, collection windows and outcomes, evidence assignments and corrections, authenticated client labels, delivery selections, receipts, checkpoints and audit metadata.
Original emails, attachments and source documents stay at their origin by design. Store stable references, not full documents, tax identifiers, account numbers, wire instructions, passwords, cookies or signed URLs carrying access secrets. A hash records the collector's asserted content version; it does not authenticate the source.
Sources and gaps
Start with an optional list or spreadsheet, or separately authorized email discovery. Muse can use its existing authorized browser access when a discovered portal needs it. The service itself does not fetch email, log into portals, bypass MFA or obtain new source permissions.
A source is supported only where the user's assistant actually has authorized access and the workflow has been tested. Named platforms are discovery possibilities, not promised integrations. An unread notice establishes availability, not collected contents. A failed or blocked check stays a coverage gap and does not erase earlier evidence.
“No new updates” applies only to a fresh, complete, successful check of the exact recorded source and date window. Saved-record retrieval is not a new source check. A quiet selected repeat does not mean the whole portfolio was checked.
Current operational boundaries
The prepared service supports bounded history, shared owner-confirmed monitoring/source preferences and public setup pages. Google sign-in, Claude connection and one welcome email passed the owner trial. Correction/history, usable private file delivery and fresh-chat retrieval for that account remain open before public access. Earlier pilot credentials remain limited to their original permissions and expiry. Check current availability with support. Each assistant needs its own source permissions. Private chat memory alone cannot preserve preferences across clients.
Automatic collection with confirmed private delivery, current Muse correction and download UX, ongoing actual retained backups, expected public operation and another consenting user's experience remain acceptance gates. No ongoing retained backup destination or schedule has been activated. A completed one-time recovery rehearsal does not promise a recovery interval.
The public launch target remains subject to approval and these gates. Operator-assisted enrollment is a proposed setup path, not an approved invitation-only or on-demand-only replacement for public enrollment.
Native connection and file acceptance
The prepared Google route creates an account on first sign-in and gives each configured assistant its own read/write connection. Existing operator-managed connections keep their original permissions and expiry. Adding another assistant uses the same Google account, with separate source permissions. Small CSVs have a prepared private file envelope; larger files have authenticated exact-byte fragments and a private assembler. Actual usable downloads in each host still need verification. No public export link or key in a URL is issued, and native tools never automatically acknowledge delivery. See native client setup and limits.
Later capabilities
Spouse, accountant and adviser sharing, emergency access, additional assistant/portal support, portfolio insights and opportunity triage remain later work. A second key for one tenant grants that tenant's scoped access; it is not selective sharing or legal authority for another person.