Vortex Memory is what turns a stateless analytics tool into a system that remembers what your business looks like. It holds two surfaces in one searchable space: a knowledge base where you upload reference files (brand guidelines, supplier catalogues, returns policies, contracts), and a reports archive where every Vortex Mind report run lands automatically. Ask Viq cites from both. The longer you use the platform, the more value the memory layer compounds — because the platform can then read patterns across months of structured data, not just the most recent run.Documentation Index
Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt
Use this file to discover all available pages before exploring further.
What lives in Vortex Memory
| Surface | What it holds | Where it comes from |
|---|---|---|
| Knowledge base | Reference files: PDF, docx, xlsx, csv, images, audio transcripts | Merchant manual upload |
| Files | The same uploaded content, accessed through a file-manager lens filtered by type, date, and owner | Merchant manual upload |
| Reports archive | Every Vortex Mind report run with full evidence, findings, and recommendations | Auto-ingested on each run |
| Concepts | The retention model, public-vs-private scope, search behaviour, and the longitudinal-insight surface | Reference documentation |
How Ask Viq cites from Vortex Memory
When you ask Ask Viq a question, it retrieves context from all three substrates — knowledge files, archived report runs, and your own chat history — and surfaces the top matches as cited context alongside its answer. You do not choose which substrate to query; Ask Viq decides based on the question. Citations always resolve through your current permissions: if you cannot see a file in the Knowledge Base, Ask Viq will not surface its contents in an answer. Every citation points to a specific source. PDF and docx citations point to the exact page. Spreadsheet citations point to the sheet and row range. Report citations point to the specific finding or evidence section within the archived run. You can click any citation to open the original source and verify what the platform based its answer on.How longitudinal pattern detection works
Every time Vortex Mind runs a report, the full output — findings, evidence, recommendations, structured JSON — auto-archives into Vortex Memory. The platform reads this archive continuously. When the same finding appears across multiple runs of the same recipe over weeks, the platform stops treating each occurrence as a one-off and starts treating it as a structural condition of your business. Three recurrence modes trigger a structural pattern:Exact ID match
Exact ID match
The same
finding_id (for example finding:PAY-AUTH-001) appears in three or more runs within 30 days. Severity and confidence are tracked across recurrences to show whether the pattern is intensifying or fading.Structural similarity match
Structural similarity match
Two findings have different IDs but describe the same underlying issue — for example, elevated declines across sibling BIN ranges from the same issuer. The platform’s similarity model groups these together. Threshold: four matching runs within 60 days.
Theme-level recurrence
Theme-level recurrence
A theme such as “checkout drop-off on mobile” accumulates enough distinct findings across runs to be flagged as a structural concern, even if no single finding ID has recurred. Threshold: six findings within the theme over 90 days.
Scope: private vs public-to-workspace
Every file you upload is per-user private by default. A file you upload is visible only to you — it does not appear in teammates’ views and does not enter their Ask Viq retrieval pool. This default is deliberate: the upload surface is safe to use for exploratory or sensitive material without every upload being visible workspace-wide. You can change scope in two ways:- Share with specific teammates — grant read-only or read-and-cite access to named users while the file stays otherwise private.
- Promote to workspace-public — make the file visible and citable by every member of the workspace.
Workspace admins can promote or demote any file’s scope for governance reasons (for example, making a departing team member’s SOP available to the workspace). Every scope change is logged in the audit trail.
Explore Vortex Memory
Knowledge Base
Upload and manage reference files — brand guidelines, supplier catalogues, returns policies, SOPs, and more.
Reports Archive
Browse, search, compare, and export the full history of auto-archived Vortex Mind report runs.