seer-shared

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Seer Shared

Seer 通用说明

Foundational knowledge for all Seer skills. Read this before using any domain skill.

所有 Seer 技能的基础知识。在使用任何领域技能前请先阅读本文。

What Seer Is

Seer 是什么

Seer is the intelligence engine behind Midaz — the Interactive Cognitive Trading Map. It tracks:

Claims — atomic evidence statements extracted from sources (the raw events/facts)
Threads — tradable angles / sub-theses built from clusters of claims
Topics — narrative domains that group related threads (e.g., "AI Infrastructure", "Energy Transition")
Global snapshot — overall market regime derived from top drivers across all topics

All queries use the

seer-q

CLI.

Seer 是 Midaz — 交互式认知交易地图 背后的智能引擎，它追踪以下内容：

Claims — 从各类来源提取的原子级证据陈述（原始事件/事实）
Threads — 由成组的声明构建而成的可交易角度/子论点
Topics — 对相关线索进行分组的叙事领域，例如 "AI 基础设施"、"能源转型"
Global snapshot — 从所有主题的核心驱动因素推导得出的整体市场状态

所有查询都使用

seer-q

CLI 执行。

The Web UI

网页 UI

Every

view_url

opens the Midaz web app — a 3D interactive map that's much easier to explore than reading JSON:

Topic sphere — click any topic node to zoom into its threads, then drill down to individual claims
Driver graph — causal links between market drivers as a force-directed network you can rotate and explore
Verdict rail — real-time regime summary with conviction level and key uncertainties

The links are deep-linkable: each

view_url

opens the map focused on exactly the right entity. Text summaries are useful, but the map shows relationships and context that's hard to convey in words — so always include the link and let the user know what they'll find there.

每个

view_url

都会打开 Midaz 网页应用 —— 这是一个 3D 交互式地图，比阅读 JSON 要容易探索得多：

Topic sphere — 点击任意主题节点即可放大查看其下的线索，还可向下钻取到单个声明
Driver graph — 市场驱动因素之间的因果关系以力导向网络形式呈现，你可以旋转并探索
Verdict rail — 实时状态汇总，包含置信度和关键不确定性信息

这些链接支持深度跳转：每个

view_url

打开地图时都会精准定位到对应的实体。文本摘要很有用，但地图能展示文字难以传达的关联和背景信息，所以请务必包含链接，并告知用户点击后能看到的内容。

Response Format

响应格式

All commands return JSON:

Success (stdout):

{ "ok": true, "data": <payload>, "meta": { "view_url": "...", "count": N } }

Errors (stderr):

{ "ok": false, "error": { "code": "...", "message": "..." } }

Access the payload via

.data

. The page-level

view_url

is always in

.meta.view_url

— read it from

.meta

, not

.data

. Per-entity URLs (e.g., each topic or thread) appear as

view_url

fields on objects inside

.data

. For raw API output (no envelope), use

--raw

所有命令都返回 JSON：

成功响应（标准输出）：

{ "ok": true, "data": <payload>, "meta": { "view_url": "...", "count": N } }

错误响应（标准错误）：

{ "ok": false, "error": { "code": "...", "message": "..." } }

通过

.data

访问响应 payload。页面级的

view_url

始终存放在

.meta.view_url

中，请从

.meta

而非

.data

读取。每个实体的 URL（例如每个主题或线索）会作为

view_url

字段出现在

.data

内部的对象上。如果需要原生 API 输出（无封装外层），请使用

--raw

参数。

Global Flags

全局参数

Flag	Default	Description
`--format`	`json`	Output format: `json` or `pretty`
`--raw`	false	Raw API response (no envelope)
`--api-url`	from config	Override API base URL

参数	默认值	描述
`--format`	`json`	输出格式： `json` 或者 `pretty`
`--raw`	false	原生 API 响应（无封装外层）
`--api-url`	来自配置	覆盖 API 基础 URL

Config & Diagnostics

配置与诊断

bash

seer-q version                  # CLI version, Go version, OS/arch
seer-q doctor                   # Verify API connectivity and config
seer-q config get <key>         # Get config value
seer-q config set <key> <value> # Set config value
seer-q config list              # Show active configuration
seer-q config path              # Show config file path
seer-q schema                   # List all command contracts
seer-q schema <command>         # Describe a command's input/output contract
seer-q health                   # API health check

bash

seer-q version                  # CLI 版本、Go 版本、操作系统/架构
seer-q doctor                   # 验证 API 连通性和配置
seer-q config get <key>         # 获取配置值
seer-q config set <key> <value> # 设置配置值
seer-q config list              # 展示当前生效的配置
seer-q config path              # 展示配置文件路径
seer-q schema                   # 列出所有命令契约
seer-q schema <command>         # 描述某条命令的输入/输出契约
seer-q health                   # API 健康检查

Common Rules

通用规则

Use
```
seer-q search
```
first whenever the user mentions a specific entity, asset, or theme
Always include
view_url
as clickable markdown links. The page-level URL is in
```
.meta.view_url
```
. Per-entity URLs (topics, threads) are on each object inside
```
.data
```
. Format as
```
[descriptive text](url)
```
— never paste raw URLs. Example:
```
[Explore this topic on the interactive map](https://www.midaz.xyz/market?topic=abc123)
```
.
Synthesize data into natural language — don't dump raw JSON
For multi-entity questions, make multiple calls to build a complete picture
When claims are asked about, note their
```
claim_mode
```
,
```
thread_role
```
(support/contradiction), and
```
event_date
```

当用户提到特定实体、资产或主题时，优先使用
```
seer-q search
```
始终将
view_url
转为可点击的 markdown 链接。页面级 URL 存放在
```
.meta.view_url
```
，实体级 URL（主题、线索）存放在
```
.data
```
内的每个对象上。格式为
```
[描述文本](url)
```
—— 绝对不要直接粘贴原始 URL。示例：
```
[在交互式地图中探索该主题](https://www.midaz.xyz/market?topic=abc123)
```
将数据合成为自然语言 —— 不要直接输出原始 JSON
针对涉及多实体的问题，发起多次调用以构建完整信息
当用户询问声明相关内容时，标注其
```
claim_mode
```
、
```
thread_role
```
（支持/反对）以及
```
event_date
```