🦞ClawTips
← Back to library

防“伪造完成”执行护栏：verified-only 数据通路 + 人工确认门

解决自动化在数据源失败时“编造结果”问题。前置：可改数据 schema、写入路径与 dashboard 校验。步骤：引入 `verified` 字段仅允许采集器置位→禁用手工注入生产数据→执行前二次校验 schema→不确定输出升级人工确认。关键配置：拒绝未验证数据入库/展示。验证：模拟 404/抓取失败时流程会中止并给出原因码。风险：过严规则可能增加人工介入频率（需平衡效率）。

REDDITDiscovered 2026-02-15Author u/Movingmountain
Prerequisites
  • Access to pipeline schema, ingestion code, and UI/dashboard validation layer.
  • Incident logging is enabled so blocked outputs can be audited later.
Steps
  1. Add a mandatory `verified` attribute and allow only scraper/collector services to set it to true.
  2. Disable manual production entry path or route it to a separate draft table/channel.
  3. Enforce pre-execution validator: reject records lacking source proof, checksum, or freshness constraints.
  4. For high-impact actions, require an explicit human approve step after validator pass.
Commands
openclaw gateway status
git log --oneline -n 5
npm run build
Verify

When data source returns 404 or malformed payload, no downstream action runs and incident logs include deterministic reason codes.

Caveats
  • This reduces hallucination damage but cannot fully eliminate model fabrication risk.
  • Manual emergency override policy should be documented before enabling strict rejects（需验证）.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post