The warehouse is the store of your own data that your server keeps on your computer. It is what an AI reads through Recued. It is what recipes work over. It exists so a question like "how is this deal doing" gets answered in one pass. That pass runs over your real data. And that data never has to live in someone else's cloud.
#Collections
| Collection | Contents | How it fills |
|---|---|---|
| Messages from your mail accounts | Synced from the provider, for example over IMAP | |
| Calendar | Events from your calendars | Synced from the provider |
| Contacts | A web of contacts, one per email address | Worked out from mail and calendar, plus ones you add by hand |
| Files | Files and message attachments | Folders you watch, and attachments that arrive |
| CRM | Snapshots of deals, contacts, and accounts | Checked against vendors such as HubSpot and Salesforce, and fixed up |
| Memory | Your own notes: facts and choices you wrote down, or let an AI save | You, under Data → Memory, or by import |
| Audit | The diary of runs, with links to the records each run touched | Written by the engine as things run |
CRM rows are snapshots. Each one sticks to a record that lives in the CRM. The CRM is still the real owner of that record. The warehouse keeps just what recipes and AI need to think locally. Vendor events, such as webhooks or a stream, make the copy fresh faster. A regular check against the vendor is the safety net.
#Enrichments
An enrichment is a fact Recued works out ahead of time and sticks onto a record. A deal's health score is one. How much you talk with a contact is one. The signals in a thread are one. Some are plain sums and counts. Some are made by AI. Every enrichment topic has its own trust setting: off, manual, or automatic. An AI-made topic never turns itself to automatic quietly. After you have run one by hand a few times, Recued suggests it. You decide to promote it.
#Housekeeping
Upkeep runs while you are not busy, as often as you pick. It packs the database down. It clears old cache. It refreshes enrichments. It checks the CRM copy against the vendor. Background AI follows each topic's trust setting and the main Pause-AI switch.
#Timelines
The links between collections power a timeline for each thing. That is one feed, in time order, for a contact or a deal. It pulls in mail, meetings, CRM changes, notes, and memory. See Audit and memory.
#Local by design
The warehouse lives in your server's data folder. It does not sync to the cloud. No part of Recued's cloud can read it. Paired devices show it on screen. The server stays in charge.
#Related
- Connections, the secret keys and addresses that feed the vendor-backed collections.