Back to Details

polaris-goal-compiler

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Polaris Goal Compiler

Polaris目标编译器

A human-AI communication protocol under WFGY 5.0 Polaris Protocol.
Compile first. Execute one active atom. Verify before unlock. Claim only what is supported.
WFGY 5.0 Polaris Protocol下的人机AI通信协议。
先编译。执行一个活跃原子。解锁前先验证。仅声明有依据的内容。

What This Is

这是什么

Polaris Goal Compiler adds the missing protocol layer between human requests and AI execution. Before producing work that looks finished, it turns the request into visible, inspectable structures:
  • Task atoms: The smallest executable units
  • Active work: What can be done now
  • Blocked work: What must wait
  • Verification gates: What must be checked before unlock
  • Truth objects: What is known vs. claimed
  • Claim ceilings: What the assistant is allowed to claim
  • Closure records: What is done, missing, partial, or unsafe
This is not a normal prompt template. It is a portable TXT-based execution protocol for making complex AI work:
  • Easier to inspect
  • Harder to fake
  • Less likely to collapse into premature completion
Polaris目标编译器在人类请求与AI执行之间添加了缺失的协议层。在生成看似完成的工作成果之前，它会将请求转化为可见、可检查的结构：
  • Task atoms：最小的可执行单元
  • 待执行工作：当前可开展的任务
  • 阻塞工作：必须等待的任务
  • Verification gates：解锁前必须检查的环节
  • Truth objects：已知内容与声明内容的区分
  • Claim ceilings：助手被允许声明的内容上限
  • Closure records：已完成、缺失、部分完成或存在风险的记录
这不是普通的提示词模板。它是一个基于TXT的可移植执行协议，可让复杂AI工作：
  • 更易于检查
  • 更难造假
  • 更不容易出现提前完成的情况

When to Use

使用场景

Use this skill before starting any of:
  • Complex creative work (writing, design, research)
  • Multi-step reasoning tasks (proofs, strategy, debugging)
  • Long-horizon projects (planning, architecture, implementations)
  • High-stakes decisions where correctness matters
  • Work involving others (code review, collaboration)
  • Theorem work or formal verification
Do not use on: trivial single-step tasks, reflex responses, simple lookups.
在开始以下工作之前使用该技能：
  • 复杂创意工作（写作、设计、研究）
  • 多步骤推理任务（证明、策略制定、调试）
  • 长期项目（规划、架构设计、实现）
  • 正确性至关重要的高风险决策
  • 涉及他人的工作（代码评审、协作）
  • 定理研究或形式化验证
请勿用于：简单单步任务、即时响应、基础信息查询。

Core Workflow

核心工作流程

1. State Your Goal Clearly

1. 清晰陈述你的目标

Write one sentence: what do you actually want to accomplish? Not the first sub-task, the end state.
用一句话描述：你实际想要达成什么？不是第一个子任务，而是最终状态。

2. Ask: Compile My Request

2. 请求：编译我的请求

Ask the AI to turn your request into:
  • Task atoms (smallest units)
  • Dependencies (which blocks which)
  • Active vs. blocked work
  • Verification gates (checks before unlock)
  • Claim ceilings (what can be claimed when)
要求AI将你的请求转化为：
  • Task atoms（最小单元）
  • 依赖关系（哪些任务会阻塞其他任务）
  • 待执行与阻塞工作
  • Verification gates（解锁前的检查环节）
  • Claim ceilings（不同阶段可声明的内容）

3. Review the Compilation

3. 审核编译结果

Before execution starts, verify:
  • Are all task atoms actually atomic?
  • Are dependencies correct?
  • Are verification gates realistic?
  • Will claim ceilings prevent overstatement?
在开始执行前，验证：
  • 所有Task atoms是否真的是原子性的？
  • 依赖关系是否正确？
  • Verification gates是否符合实际？
  • Claim ceilings是否能防止过度声明？

4. Execute One Active Atom

4. 执行一个活跃原子

Work on ONE task at a time. After each:
  • Verify before moving to the next
  • Check against claim ceiling (don't overstate readiness)
  • Move blocked tasks to active only if dependencies are met
一次只处理一个任务。完成每个任务后：
  • 验证通过后再进行下一个任务
  • 对照Claim ceilings检查（不要过度声明完成度）
  • 只有当依赖条件满足时，才将阻塞任务转为待执行状态

5. Iterate

5. 迭代

After each atom completes, return to step 4 until all atoms are done.
每个原子任务完成后，回到步骤4，直到所有原子任务完成。

Key Concepts

核心概念

Task Atoms

Task atoms

The smallest executable unit that:
  • Can be completed in one session
  • Has clear entrance and exit criteria
  • Produces something verifiable
  • Does not depend on incomplete tasks
最小的可执行单元需满足：
  • 可在一个会话内完成
  • 有明确的开始和结束标准
  • 产生可验证的成果
  • 不依赖未完成的任务

Active vs. Blocked Work

待执行与阻塞工作

  • Active: Ready to start, all dependencies met
  • Blocked: Waiting on something else to finish first
Clear separation prevents fake progress (looking busy on wrong things).
  • 待执行：已准备好启动，所有依赖条件已满足
  • 阻塞：需等待其他任务完成才能开始
明确区分可防止虚假进展（在错误的事情上看似忙碌）。

Verification Gates

Verification gates

What must be checked before moving forward:
  • Does this output match what was asked for?
  • Is it complete enough for the next task?
  • Are there hidden assumptions?
  • What could break downstream?
在推进前必须检查的内容：
  • 输出是否符合要求？
  • 对于下一个任务来说是否足够完整？
  • 是否存在隐藏假设？
  • 哪些问题可能影响后续流程？

Truth Objects

Truth objects

What must actually become true for the work to count as done, as opposed to prose that merely reads as if it were true. A verification gate passes against a truth object, not against a well-written paragraph.
工作被视为完成必须满足的实际条件，而非仅仅是读起来像完成的文字内容。Verification gates需对照Truth objects验证，而非对照写得好的段落。

Claim Ceilings

Claim ceilings

Honest limits on what can be claimed:
  • "Complete" means verified to work end-to-end, not "looks finished"
  • "Correct" means checked against requirements, not "sounds right"
  • "Ready" means tested for the next stage, not "looks polished"
Over-claiming (saying something is done when it's only drafted) is the most common trap in AI work. See 
references/claim-ceiling-examples.md
for concrete examples in different contexts.
对可声明内容的诚实限制：
  • “完成”指经过端到端验证可正常工作，而非“看起来完成”
  • “正确”指符合要求检查，而非“听起来合理”
  • “就绪”指通过下一阶段测试，而非“看起来精致”
过度声明（仅完成草稿就称已完成）是AI工作中最常见的陷阱。不同场景下的具体示例请查看
references/claim-ceiling-examples.md
。

Closure Records

Closure records

For each atom, record what is done, what is missing, what is only partially true, and what is still unsafe to claim. A closure record preserves continuity across rounds so that unfinished work stays visible instead of being buried in prose -- this is what stops a local step from being promoted into fake global completion.
针对每个原子任务，记录已完成、缺失、仅部分正确以及仍存在声明风险的内容。Closure records可确保多轮会话的连续性，让未完成的工作保持可见，而非被文字内容掩盖——这正是防止局部步骤被错误当作全局完成的关键。

Interaction with Other Skills

与其他技能的交互

With WFGY-Method (Drift Control)

与WFGY-Method（漂移控制）

  • Goal Compiler structures the work (what to do)
  • WFGY-Method keeps you on track (why you're doing it)
Use Goal Compiler first to atomize, then apply WFGY-Method while executing each atom.
Integration: Goal Compiler's "verification gate" becomes a checkpoint for WFGY-Method's BBCR (bounded retry).
  • 目标编译器构建工作结构（要做什么）
  • WFGY-Method确保工作不偏离轨道（为什么要做）
先使用目标编译器进行原子化处理，再在执行每个原子任务时应用WFGY-Method。
集成方式：目标编译器的“Verification gates”成为WFGY-Method的BBCR（有限重试）检查点。

With Fifth-Dimension Engine (Problem Solving)

与Fifth-Dimension Engine（问题解决）

  • Goal Compiler specifies the problem clearly
  • Fifth-Dimension Engine solves/structures it
  • Goal Compiler's verification gates check the engine's output
Use Goal Compiler to compile the problem statement, then dispatch to Fifth-Dimension Engine.
Integration: Fifth-Dimension Engine's "route" output maps to Goal Compiler's task atoms and verification gates.
  • 目标编译器清晰定义问题
  • Fifth-Dimension Engine解决/构建问题
  • 目标编译器的Verification gates检查引擎的输出
使用目标编译器编译问题陈述，再交由Fifth-Dimension Engine处理。
集成方式：Fifth-Dimension Engine的“route”输出对应目标编译器的Task atoms和Verification gates。

References

参考资料

See 
references/
directory for:
  • task-atomization.md
    -- how to break work into atoms
  • verification-gates.md
    -- designing verification for each stage
  • claim-ceiling-examples.md
    -- what "complete" actually means in different contexts
  • skills/polaris-protocol/SKILL.md
    -- the Polaris Protocol tree root and state machine that wires this skill to Fifth-Dimension Engine and WFGY-Method
请查看
references/
目录下的内容：
  • task-atomization.md
    ——如何将工作拆分为原子任务
  • verification-gates.md
    ——为每个阶段设计验证环节
  • claim-ceiling-examples.md
    ——不同场景下“完成”的实际定义
  • skills/polaris-protocol/SKILL.md
    ——Polaris Protocol的根目录和状态机，将该技能与Fifth-Dimension Engine和WFGY-Method关联

What This Is Not

这不是什么

This skill does not:
  • Solve the problem (that's Fifth-Dimension Engine)
  • Control drift during execution (that's WFGY-Method)
  • Replace thinking (it enhances it by making structure visible)
  • Guarantee success (only guard against fake completion)
  • Claim to be the full WFGY 5.0 system (it is one public protocol component; the upstream engine is the main product surface)
该技能不会：
  • 解决问题（这是Fifth-Dimension Engine的功能）
  • 控制执行过程中的漂移（这是WFGY-Method的功能）
  • 替代思考（它通过让结构可视化来辅助思考）
  • 保证成功（仅能防止虚假完成）
  • 声称是完整的WFGY 5.0系统（它只是一个公开协议组件；上游引擎是主要产品界面）