Your record. Your sources. Your assistant.

Pref workflow contract

Begin with getting started and Muse setup. This is a maintained factual record used through your own assistant. Public enrollment is being prepared; no schedule or new access is activated by this document.

Inventory and ownership

Start with an optional list/spreadsheet or bounded discovery through your own authorized sources. Seeds and invitations are candidates. Confirm exact owners, vehicles and holding evidence before real import. Read existing records first and reuse their investment/owner keys. Unknown values remain unknown; different legal owners remain separate positions.

Useful updates

Pref defaults to one concise update about the relevant investment. It reuses saved context and checks that item's sources; flagging something does not trigger a whole-portfolio scan. Ask for more detail or a broader review when you want it. Private investments are not a daily market feed, and there is no default daily portfolio scan.

Read coverage before collection and agree on the exact source/window. An LP letter contains substantive manager narrative, not merely an account statement, capital-call notice or tax-availability email. Save concise facts, references, reporting periods and the collector's content hash. Source documents stay at origin. Failed, blocked and unread checks remain explicit gaps.

Lead with company progress, financing/exits, fund activity and material problems, with sources and dates. Flag a sourced capital call once unless the user requests a reminder or materially new information arrives. Showing a notice does not prove payment. Keep performance secondary and tax-document checks optional.

Recognizable Pref updates

Start each Pref-backed update with A note from Pref, even in plain text. When an assistant mixes topics, keep this heading with the Pref section or each separately delivered Pref message. A light opener is optional: “Pref here—quick update on [investment].” Then give the sourced development, any explicit action, source and reporting date, and relevant coverage gaps. Keep the voice warm and restrained. Label only updates grounded in Pref records or an explicitly authorized Pref workflow; unrelated assistant messages keep their own identity. The label does not imply Pref independently accessed email, verified a fact, sent anything or completed an action. Preserve uncertainty and the actual assistant’s role. Formatting never changes selected evidence or delivery/ACK rules.

Delivery and continuity

Prepare only the saved versions actually shown. Acknowledge their exact selection only after confirmed destination receipt. A broad first briefing can contain all history; showing one letter does not authorize acknowledging the batch. Retry with original IDs/body and preserve remaining history. A quiet selected repeat says nothing about unchecked sources.

Fresh clients of the same investor retrieve the same stored record and corrections. Different investors remain isolated. Correct or retract a specific document using its current expected assignment and a sourced instruction. Preserve original extraction/history. Reusable exact future-version rules require separate writer authorization; similar names do not authorize remapping.

Tell your assistant which holdings or sources to skip and whether you want routine capital-call flags. In the prepared release it can show the current structured preferences, confirm your change, and save it to your private shared record. Another authorized client of the same investor then reads the same preferences before routine collection. A declined source is skipped; turning off a flag does not mark an obligation paid or resolved. Source access, schedules and destinations still require their own permission. Preferences held only in chat memory do not carry this guarantee.

Export and operational limits

CSV should become a usable private file in Muse; exporting consumes no delivery state. Complete JSON history may require bounded pages. A partial result is not a complete export.

Send a copy to Google Sheets

Ask your assistant: “Send my current Pref spreadsheet to Google Sheets. Show me the destination and who can access it before writing.” Authorize your own Google Drive/Sheets connection separately, choose a new private spreadsheet or a specific empty tab/range, and confirm the proposed write. A Pref credential gives no Google account permission.

The assistant first downloads the complete CSV, retains the headings and blank unknowns, and previews the destination and row count. With a supported Google Drive connection it can import that CSV as a new native Google Sheet. For a chosen existing Sheet it reads tab metadata and the exact target range, asks before replacing any existing content, and writes only the approved cells as literal values. It then reads those cells back and gives you the Sheet link, timestamp and any mismatch. No public link, new collaborator, recurring sync or delivery acknowledgement is created by this export.

If Muse's current connection cannot write or verify Google Sheets, it must report that gap. You can use the same private CSV in a supported connected assistant you separately authorize, or open Google Sheets, create a private blank spreadsheet and use File → Import → Upload with that CSV. Review the imported headings, rows, blanks and sharing settings. This is a copy of the saved record at that time; future updates need another explicitly requested export. The client recipe gives the supported connector procedure. An actual user's Sheet write is separate acceptance, never inferred from these instructions.

Automatic collection with private receipt, current Muse correction/download UX, ongoing retained backups and another consenting user's complete setup remain operational acceptance gates. These instructions promise no unattended schedule, source completeness or recovery interval. Spouse/accountant sharing is later work.

Using Pref in Muse · Current capabilities · Detailed client recipe · Support