Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Sovereignty: fw task review emits a hardcoded 'go' verb next to a NO-GO rationale

オープン
  • 何か問題がありますか？
#82 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
54/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
shell
領域
cli, developer-experience

調査の方向性

Read lib/review.sh at emit_review and lib/inception.sh around line 401 for the accepted decision verbs. Check how recommendation lines are extracted and how the existing verb validation handles an inert placeholder; then run or recreate the reported fixture cases, including absent and unclassifiable recommendations. Done means the emitted command does not prescribe a decision that contradicts the recommendation and remains safely rejected when it cannot classify one.

索引モデルが issue の本文から書いたものです。

説明

Context

  • Framework version: 1.6.258
  • Project: 050-email-archive (shared-tooling mode)
  • Reported: 2026-09-28T17:35:47Z

Description

emit_review in lib/review.sh prints a copy-pasteable decision command for every inception task. The verb is a string literal go, while --rationale is interpolated from the task's own **Recommendation:** line:

echo "    $(_fw_cmd) inception decide $task_id go \\"
echo "    --rationale \"${_rec_line}\""

So an inception recommending NO-GO hands the human a ready-to-paste command that RECORDS GO carrying a rationale that reads NO-GO. The rationale is what lands in the audit record, so the artefact contradicts itself. This is a sovereignty boundary: the verb is the human's decision, and the tool pre-fills it wrongly.

MEASURED BLAST RADIUS (two independent consumer projects):

  • 050-email-archive: 48 of 116 inception tasks carrying a recommendation (41%) emit the contradiction — 16 NO-GO, 32 DEFER. A further 21 tasks have no recommendation line at all and got go beside the placeholder rationale 'your rationale'.
  • 010-termlink measured 51 of 245 independently.

SUGGESTED FIX: derive the verb from the recommendation's LEADING token, anchored rather than substring-matched, and refuse to guess otherwise. go | no-go | defer is already the accepted vocabulary (lib/inception.sh:401), so all three classes map exactly and nothing is invented.

Anchoring matters in BOTH directions: 'NO-GO' contains 'GO', and prose like 'Do not go ahead until X' contains 'GO' while meaning the opposite. A substring test gets both wrong.

When the recommendation is absent or unclassifiable, emit an inert placeholder token rather than a verb. Note that <go|no-go> is a poor placeholder: pasted into bash it is a stdin redirect plus a pipe, so it fails messily for the wrong reason. A bare uppercase token like DECISION is shell-inert and is rejected cleanly by the existing verb check.

We have applied this locally as a vendored patch and pinned it with a 21-assertion fixture suite that drives the real emit_review (including a negative control sourcing the pre-fix version from git, and a live-corpus pass over all 137 inception tasks). Happy to raise a PR if useful.

Reported via fw upstream report from field installation

主要言語
Shell
スター
16
フォーク
6
平均マージ
6時間 24分
マージ済み PR（30日）
5

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

DimitriGeelen/agentic-engineering-framework のほかの issue

DimitriGeelen/agentic-engineering-framework の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。