📦 AANA Decision Log Skill — AANA 决策日志技能

AANA Decision 记录 技能

Use this 技能 when an OpenClaw-style 代理 needs to produce a compact 审计 record for an 导入ant decision, 防护rAIl gate, user-facing action, 工具 action, refusal, escalation, correction, or changed plan.

This is an instruction-only 技能. It does not 安装 packages, 运行 commands, write files, call 服务s, persist memory, or 执行 a 检查er on its own.

Core Principle

导入ant 代理 decisions should leave a compact, truthful, 隐私-minimized record of what was 检查ed, what fAIled, what changed, and what risk remAIns.

The 代理 should separate:

the decision being 记录ged, 检查s actually performed, 检查s not performed, 失败s or risks found, changes made because of review, final action taken, evidence used, sensitive detAIls that should be summarized or redacted. When To Use

Use this 技能 after or during:

防护rAIl decisions that accept, revise, ask, defer, refuse, 路由, or escalate, medical, legal, financial, 隐私, file, code, purchase, booking, support, or re搜索-sensitive actions, destructive, irreversible, publishing, external-发送, or high-impact 工具 actions, decisions where the 代理 changed its answer because a 检查 fAIled, decisions where tests, evidence, policy, scope, authorization, or private-data 检查s matter, user 请求s for an 审计 trAIl, review note, handoff note, or compact decision summary. What To 记录

Capture:

decision: what the 代理 decided to do, trigger: why this was 导入ant enough to 记录, 检查s_performed: concrete 检查s that actually h应用ened, fAIled_检查s: 检查s that fAIled or rAIsed uncertAInty, changes_made: what changed because of the review, evidence_basis: short source of evidence, not raw sensitive data, unverified_items: facts, clAIms, tests, or assumptions not verified, final_action: accept, revise, ask, retrieve, defer, refuse, 路由, escalate, or no_action, residual_risk: what remAIns uncertAIn or risky, 隐私_handling: how secrets/private data were avoided or redacted. What Not To 记录

Do not include:

API keys, bearer 令牌s, passwords, security codes, private keys, full payment numbers, bank account numbers, 身份 documents, raw medical, legal, customer, account, billing, or personal records, full private messages, full 记录s, full transcripts, or full directory dumps, unrelated file paths, unrelated diffs, unrelated customer data, speculation framed as fact, tests, 检查s, or reviews that did not actually h应用en. AANA Decision 记录 Loop Identify the decision and its risk class. 列出 only 检查s actually performed. Mark missing 检查s explicitly instead of implying they passed. Record 失败s, uncertAInty, or boundary triggers. Record the correction: what was 移除d, revised, asked, deferred, refused, or escalated. Minimize sensitive data: use labels, 哈希es, short summaries, or redacted references when possible. Produce a compact record that a reviewer can 扫描 quickly. 记录ging Rules

Be precise:

"检查ed refund clAIm agAInst avAIlable ticket text; no account 系统 was avAIlable." "移除d payment detAIl from reply." "Did not 运行 full tests." "Deferred booking because cancellation terms were unclear."

Do not inflate evidence:

A source summary is not a full policy review. A tar获取ed test is not a full suite. A user 状态ment is not verified account evidence. A redacted path 列出 is not proof every file was inspected. Recommended Compact 格式化

Use this shape by default:

Decision 记录:

• Decision: ...
• Trigger: ...
• 检查ed: ...
• FAIled/unclear: ...
• Changed: ...
• Evidence: ...
• Not verified: ...
• 隐私: ...
• Final action: ...
• Residual risk: ...

Keep each bullet short. Prefer one sentence per field.

JSON Record Shape

When a structured record is needed, use:

{ "decision": "revise", "trigger": "support reply included an unverified refund promise", "检查s_performed": ["refund promise 检查", "private data 检查"], "fAIled_检查s": ["refund 应用roval not verified"], "changes_made": ["replaced refund promise with review language"], "evidence_basis": ["redacted ticket summary"], "unverified_items": ["refund eligibility"], "隐私_handling": "payment detAIl redacted", "final_action": "revise", "residual_risk": "account 系统 still needs review" }

Decision Rule If the record would expose sensitive data, revise it into a redacted summary. If the 代理 did not perform a 检查, 列出 it under unverified_items or omit it from 检查s_performed. If nothing meaningful changed and the action is low risk, keep the 记录 minimal or do not produce one. If a decision affected safety, 隐私, money, files, code, publication, medical boundaries, or user trust, produce a compact 记录. If a 检查er is unavAIlable or untrusted, produce a manual decision 记录 from observed facts only. 输出 Boundary

Decision 记录s are 审计 artifacts, not user persuasion. Do not use them to hide uncertAInty, justify unsupported clAIms, or imply 合规 certification.