docs: record Seth's keep-as-built answers (Gitea issues 6, 10, 14, 15, 16, 22, 26, 28, 29)

Issue 6 keeps every tightening row except filing for packets routed to Shipping, which is still asked on the issue. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-27 14:57:34 -06:00
parent 9764e5d11c
commit 8e69b38e0b
3 changed files with 13 additions and 9 deletions
@@ -995,6 +995,8 @@ On a draft made by the feed that is flagged (or already has a hand upload), Cler

 The old policy was looser than the old screens in places. The rebuild follows the screens where they were stricter, and the README where it states the intent. Each row is a change Seth can veto.

+SethD answered on 2026-10-26: the rows are kept as shown (Gitea issue 6), the data book date (issue 14), the withdrawn verification and ITP initials rows (issue 15), both release rows (issue 16) and the block signature row (issue 26). One row is still asked on issue 6: filing for packets routed to Shipping.
+
 | What the old build allowed | What the rebuild does | Why | Can be vetoed |
 |---|---|---|---|
 | A department lead could write welds, BOM, heat tags, the checklist, stage fields and the clock through the policy whenever the packet was in a shop status. | These edits need the holder of the packet (the holder rule, applied as the old screens did). A lead of another department cannot. | The screens only offered these to the holder. The policy now matches. | Yes |