...
Structured memory cards currently available in the file-backed layer.
This is not a decorative chat page. It is the central memory layer for research, strategy, signals, execution logic, and module routing across the Ztrader system.

A central memory layer should show its inventory, not just pretend it knows things.
Structured memory cards currently available in the file-backed layer.
Frameworks, notes, playbooks, and primers connected to memory objects.
Latest logged queries written through the query route and dynamic API layer.
Current top objects available in the local memory spine.
The system should remember what has been asked, not just what looks pretty.
These modules should eventually read from and write to the same memory spine instead of behaving like separate little kingdoms.
Cross-asset macro notes, event frameworks, rates, FX, commodities, and geopolitical stress mapping.
Volatility structure, options playbooks, earnings setups, skew, term structure, and scenario mapping.
Execution logic, liquidity windows, bid/ask microstructure, flow interpretation, and forced unwind signals.
Earnings framework, gap logic, post-print behavior, positioning, and cross-sector sensitivity analysis.
Structure phase, momentum bias, candle context, support/resistance, and annotated market map generation.
Factor logic, signal definitions, backtest modules, ranking engines, and screening workflows.
CTA, macro, event, execution, and hybrid strategy pods linked to regime-aware memory objects.
Shock regime handling, position discipline, execution risk, scenario stress, and portfolio constraint logic.
Cards are the useful unit. Not just random chunks floating in a vector swamp.
Hormuz chokepoint, logistics shock, physical supply repricing, and macro spillover path.
Direction filter first, vulnerable liquidity window second. Trade only when both blades align.
Dollar funding stress, basis pressure, intervention risk, and cross-border balance sheet tension.
Pre-print setup, implied move, post-gap behavior, and failure patterns after the first hour.
The future RAG core should not be “chat only”. It should route between retrieval, graph, structured data, and tool modules.
Documents, chunks, cards, graph edges, citations, and structured research objects.
Ask, research, strategy, data, and module-launch requests are routed through different retrieval paths.
Macro, options, order flow, quant, charts, and risk tools should all consume one shared memory spine.