投资市场跟踪 Market Watch

Schema document — read at the start of every market-watch session. This space is for time-sensitive market observation, not permanent investment knowledge.

Scope

What this space covers:

• 交易日早报、午报、晚报
• 盘面方向、资金流向、强弱变化
• 7天 / 1个月 / 3个月观点变化
• 短期主题、催化剂、失效条件
• 当日建议、观察指标、风险提示

What this space deliberately excludes:

• 长期投资哲学
• 已经抽象化的资产配置框架
• 不带日期的永久结论
• 未注明来源和时点的观点

Relationship With Wiki

This space is the time-sensitive layer.

LLM Wiki/全球资产配置/wiki/ is the durable knowledge layer.

Rules:

• Daily observations stay here first.
• A view can be promoted to wiki only after repeated evidence across time.
• Market Watch records "what is happening now".
• Wiki records "what remains useful after the noise fades".
• Do not turn a one-day market move into a permanent concept.

Directory Structure

• 00-首页 Dashboard.md — Market Watch entrance
• daily/YYYY/YYYY-MM-DD.md — one trading day per note
• rolling/过去7天.md — short-term view changes
• rolling/过去1个月.md — monthly main lines and attitude changes
• rolling/过去3个月.md — quarterly policy and theme evolution
• themes/ — time-sensitive market themes
• raw/YYYY/ — original daily inputs
• scripts/build_free_site.sh — builds a free password-protected Cloudflare Pages version under web/dist
• scripts/deploy_free_site.sh — deploys the free Cloudflare Pages version after Cloudflare login/project setup
• scripts/publish_market_watch.sh — optional Obsidian Publish helper, kept for paid Publish fallback only

Required Fields

Every daily note should include:

• 日期
• 市场状态
• 今日主线
• 风险偏好
• 早报 / 午报 / 晚报
• 方向与态度
• 拐点与变化
• 建议与失效条件
• 今日新增来源
• 可沉淀到 Wiki 的候选逻辑

Every theme note should include:

• 当前态度
• 强度
• 开始日期
• 最近更新
• 结束/失效条件
• 观点时间线
• 核心观察变量

Web Publish Rule

The user wants the Market Watch space to be available as a public webpage for other users, and prefers a free solution.

Free publish stack:

• Build the full LLM Wiki/投资市场跟踪/ directory into web/dist.
• Use Cloudflare Pages free hosting.
• web/functions/_middleware.js currently allows public access. If the user later wants password protection, re-enable HTTP Basic Auth there and add Cloudflare Pages environment variables SITE_USER and SITE_PASSWORD.

After daily maintenance:

• Run scripts/build_free_site.sh to refresh the local website.
• Once Cloudflare is logged in and the Pages project exists, run scripts/deploy_free_site.sh to publish publicly.
• If deploy is not configured yet, still complete daily maintenance and tell the user the site was built locally but not deployed.