E1.1.3 Carry the sign-off id into writer jobs and change records #26

Activity

1. CompleteDotTech

   added

   area/t3-consentCo-owner (T3) sign-off and consent gatesCo-owner (T3) sign-off and consent gates

   rollout-findingFound while rolling the showcase out to Pick-Your-AIFound while rolling the showcase out to Pick-Your-AI

   on Oct 30, 2026
2. CompleteDotTech

   added the

   Task

   issue type on Oct 30, 2026
3. CompleteDotTech

   added a parent issue on Oct 30, 2026

   • T3 sign-off is trust-only: no record is read or verified #23
4. CompleteDotTech commented on Oct 31, 2026

   

   CompleteDotTech

   on Oct 31, 2026

   ContributorAuthor

   More actions

   Clarification on the field name for this subtask (no change to the acceptance criteria).

   #26 says "add approval_id to jobs created under the flag". In the implementation in PR #123, writer jobs and change records carry the sign-off as signoff_id (and signoff_ids when several grants apply), and approval_id is never set from a sign-off: approval_id names the decisions/APPROVED_ACTIONS.yaml row that the writer guard looks up, so reusing it would blur two different records. Please read the #26 subtask as "carry the sign-off id as signoff_id". The behavior is documented in references/t3-signoff.md and SKILL.md, and covered by the tests in PR #123.

   Prior work: no earlier comment on this issue; PR #123 is the only PR covering it. Evidence of the exact-head validation will be in that PR; this comment is a clarification only and is not an approval of the PR.

   🤖 Generated with Claude Code
5. CompleteDotTech

   added a commit that references this issue on Oct 31, 2026

   Hold withdrawn repositories in T3 org profile, pins and captured Org …

   ...

   84f7a94