The Desgarde Journal
Intelligence,
considered.
A closer look at the decisions behind private intelligence, institutional knowledge and digital trust. Written for the people responsible for them.
Explore the primary sources
Private AI
A private intelligence layer for the family office.
A family office archive carries professional secrecy, anti-money laundering retention and data protection duties at once. The design follows: inventory first, access by role, answers with citations, human sign-off and retention set by document class.
Private Workplace
A private workplace, with a clear perimeter
A private workplace is defined by who can reach what, how they prove it, and what happens when access changes. Investor portals apply the same rules, investor by investor.
Operations
An air gap is an operating discipline
Isolation moves security work from the network to people and procedure. This is the maintenance routine an isolated AI appliance needs, and the hardware arithmetic behind it.
Transactions
Discretion across a complex transaction.
Monaco’s anti-money laundering law names the sale and rental of large pleasure vessels and aircraft, and deal files carry personal data under Law No. 1.565. A working model: role-based data rooms, a separate KYC vault, cited answers, no speculative profiling, and transfers mapped before documents move.
Governance
Monaco’s new data protection landscape.
Monaco’s 2024 data law moved institutions from prior registration to demonstrable accountability. A practical reading of the authority, the obligations, the open transition window, the transfer regime and how each duty maps to system design.
Relationships
Relationships deserve better infrastructure.
Relationship notes are personal data. A discreet pipeline sets a lawful basis per purpose, treats objections as hard stops, respects Monaco’s email prospecting rule, records where each introduction came from, and keeps AI in a drafting role with human approval.
Sovereign Infrastructure
What sovereign AI actually requires
Sovereignty is a set of separate controls, not one feature. This piece separates the terms, sets out a practical threat model, and places the CLOUD Act where it belongs.
Private AI
Your AI should know its boundaries
A private assistant is only as safe as its retrieval layer. Permissions are checked before the model sees a passage, and a named person stays accountable for the answer.
Governance
Private infrastructure should leave you free to move
Owning the hardware is not the same as owning the system. A firm is free to move when it holds the keys, the data in open formats, the records of how it was built, and a handover it has rehearsed.
Private Workplace
A private capital portal should explain as well as protect
A portal that only locks documents away sends clients back to email for every explanation. One that dates each figure, names its source, shows who has access and mirrors the rules on mandates earns its place. A design reading of Monaco’s data protection texts and current authentication guidance.
Private AI
Better answers begin with better documents
A private AI system answers from what it is given. Drafts beside final versions, crooked scans and unlabelled files all reach the answer. Most of the quality work happens before indexing.
Governance
Who is accountable for the family office’s AI?
Most family offices already use AI; few can say who owns each use. Law No. 1.565 makes the controller accountable, the MFO law adds secrecy and supervision, and the EU AI Act can reach Monaco when outputs are used in the Union. Governance means named owners, a register and a human at the points that matter.
Private AI
Private intelligence across languages
A firm that works in several languages needs a system that retrieves across them, answers in the right one, and never lets a translation stand in for the source.
Governance
Retention is a design decision, not an archive setting
A retention policy that says “keep everything” fails the data protection law. One that says “delete after five years” fails the moment nobody knows when year one began. Retention works when each record carries its purpose, its trigger date and its end-of-life action.
AI Evaluation
How to know if a private AI system is useful
A demonstration shows what a system can do once. An evaluation shows what it does on your questions, over your documents, with your permissions, every time it changes.
Institutional Presence
What an institutional website needs to earn trust
An institutional website earns trust through verifiable details, restraint in what it collects, a domain that cannot be spoofed and a hard line between public pages and private client access. A working list for Monaco firms, grounded in texts in force in early 2026.
Operations
A backup is only the beginning of recovery
A copy of the data answers one question: what can we get back? Recovery answers two more: how recent, and how soon. Those answers belong to the firm, and a planned restore test is the most direct way to check them.
Private AI
Private legal knowledge, with its boundaries intact
Precedents, opinions and correspondence make a firm’s knowledge valuable. Secrecy, matter walls and the line Law No. 1.362 draws between advice and transactions make it dangerous to pool. A design that keeps each boundary in the index, not only in policy.
Sovereign Infrastructure
Size the workload before the machine
A GPU order is the last step of sizing, not the first. Start from the questions, the documents and the people who will ask them, then do the memory arithmetic.
Governance
Cross-border data: the decisions behind a Monaco architecture
A Monaco firm does not choose one transfer regime. It chooses, flow by flow, which destinations it accepts and which safeguard each one needs. A practical reading of Law No. 1.565, its July 2025 ordinance, and the EU and US rules that meet it.
Research dates identify the period covered. Each article also gives its actual publication date and links to the original sources. For advice on your firm’s specific obligations, involve your qualified advisers.