> For the complete documentation index, see [llms.txt](https://solari-finance.gitbook.io/solari.finance-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solari-finance.gitbook.io/solari.finance-docs/one-solari-id-two-workspaces.md). # One Solari ID, Two Workspaces A unified Solari relationship connecting Vault Desk and GoldStackz without making either a prerequisite. ### One Relationship with Solari A customer should not need disconnected identities and histories to use different parts of a modern gold platform. One Solari ID connects the relationship while preserving two distinct experiences for different participants and purposes. Vault Desk leads as the flagship professional workspace; GoldStackz extends protected ownership through accessible Digital Gold Bills. Vault Desk is the principal Solari environment for sXAU, Gold Pools, GoldNotes, settlement, evidence, delivery, the Gold Credit Line, and elective SUSD Yield. GoldStackz serves everyday accumulation, collecting, and meaningful gifting through fixed-denomination DGBs. A customer may use either workspace or both. Neither is a prerequisite for, or an upgraded version of, the other. What connects them is more important than a shared login. Holdings, funding, SUSD, receipts, activity, evidence, delivery records, membership, messages, and continuity remain organized through one Solari identity. The two workspaces feel different because their audiences are different; the ownership principles underneath them remain disciplined and consistent. *** *** ### A Comprehensive MVP Solari has developed a high-fidelity MVP that brings the complete GoldLink System into one integrated experience. It demonstrates how products, balances, evidence, settlement, delivery, credit, Yield, membership, and reporting work together before production deployment connects the system to live institutional rails. ![](https://content.gitbook.com/content/foyvsiE4j1HR210JM2nP/blobs/yAhGF1OCZJy60BZAhBV9/assets/current-account-snapshot.png) **Illustrative MVP account overview:** gold holdings, funding, SUSD, Gold Pools, Yield, and Gold Credit Line status in one connected view. *Figures and account states shown in the MVP are simulated for demonstration and are not connected to real gold, funds, or bank accounts.* The complete platform logic has been made tangible. A prospective partner, investor, provider, or institutional participant can experience acquisition and sale journeys, pool reservations, GoldNote lifecycle states, DGB gifting and claims, sXAU evidence and delivery review, SUSD movements, elective Yield, collateral locks, membership benefits, receipts, reporting, and continuity instead of imagining their relationships from a diagram. Production deployment will require real-world integration, adaptation, hardening, reconciliation, and operational design around the selected custody, banking, payment, cryptocurrency, compliance, logistics, credit, and Hedera connections. The MVP's achievement is that those moving parts already have a coherent platform model to connect to. *** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://solari-finance.gitbook.io/solari.finance-docs/one-solari-id-two-workspaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.