计划执行与检查节点
executing-plans
按既定实施计划完成工作,保持过程检查和反馈。
corpus-grounding-expander【效率与协作】Fetches and normalizes multi-version public-domain corpora into a single verified-axiom store for verbatim-relay grounding, recording per-version license and provenance.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Builds or broadens the grounded axiom a relay system quotes from. When a system's output must be constrained to verbatim source (fail-closed grounding), the corpus IS the axiom — this skill expands that corpus from multiple public-domain versions so grounding is robust and non-biased (a quote verified in ANY version counts), without ever adding a generator.
Origin: harvested from the-bible (2026-06-20) — 6 public-domain Bible versions, 197k verses, as the fail-closed grounding axiom. The grounds, inline, because the harvest record does not ship: one edition's wording makes a fail-closed check reject a faithful quote that followed a different edition, so the union across versions is what stops fail-closed grounding from failing closed against the user — and it keeps one translation's editorial choices from silently becoming the axiom. Generalizes to any verbatim-relay corpus (legal statute, RFC text, standards). Full harvest record — hub-local, not distributed in the npm package:
tracks/_contrib/field_harvest_2026-06-20_gate-locality-and-grounding-capabilities.md.
/corpus-grounding-expander {source or version}ref → text) so cross-version quotation stays aligned. Write per-version files +
an _index recording version id, license, scope, and record count.probe_status:. Writing the probe spec
without running it is probe_status: not_run, not a pass.fetched | failed(<reason>) | skipped(<reason>) | unknown. A version that was tried and dropped appears with its reason; absence from the list is not a zero, it is an unrecorded drop. Check class: mandatory-pass (binary — the attempted-version list is present and every entry carries one of the four statuses).canon_scope: — the reason plus the explicit list of affected keys and versions. An unrecorded exception is FAIL: "it's canon-scoped" asserted in prose and nowhere in the index does not satisfy this condition.probe_status: executed plus the attached refusal output). A probe spec with no run is probe_status: not_run and is a sub-condition, never this one. Degrade — labeled, never a silent pass: no consumer gate exists yet → record probe_status: no_consumer (<what is missing>); the corpus may still ship, but ships labeled relay-unverified, this condition stays UNMET, and nothing downstream may cite the corpus as relay-verified until a run is attached.Yes — needs only a network fetch + file write. No dependency on other FH skills (a consumer gate that reads the corpus is the system's own, not this skill's).