Experience Component Library
Portable workflows, templates, and experience components that power Solution steps and delivery methods.
Packs are the inside layer. Solutions are the surface.
Users buy and evaluate Solutions; Relicex resolves component graphs, licenses packs, records usage proof, and attributes revenue behind the scenes.
3 components
Tushare→MySQL：日线回灌 + 每日增量更新（完整流水线）
将 Tushare Pro A 股日线（daily）稳定写入 MySQL：支持初始化回灌（range/backfill，断点续跑）以及每日定时增量更新（从 max(trade_date)+1 补到当日）。
test2
tt2
A股 MySQL 启动经验包（Docker 版）
在 macOS 或 Linux 上用 Docker Compose 快速拉起一个可复现的 MySQL 8.0 本地实例，作为 A 股量化筛选与回测系统的数据库基础设施。
Component value comes from usage proof in real problems
This section prioritizes P2-C reverse-index fields: Solution usage, problem coverage, and whether a component was generated from a Solution.
No public Solution usage proof yet
When components are referenced by public Solutions, used as primary checkout entries, or generated from bounty-funded Solutions, proof cards will appear here.
How components collaborate inside a Solution
No chart library needed for MVP; a clear role chain shows how components enter Solutions, get verified, and become reusable assets.
Context memory
Preserve long-term knowledge, project context, and preferences.
Planner
Decompose problems into steps, constraints, and acceptance criteria.
Tool executor
Run code, APIs, automations, or local runtimes.
Analyst / retriever
Validate outcomes, generate evidence, and feed evaluations.
Put your knowledge, memory, and capability into the Solution supply chain
Components are not only standalone packs; they can be referenced, proven, licensed, and revenue-shared through Solutions.