Policy tightenings against the old build (ten rules to keep or veto) #6

New Issue

2026-10-19T02:50:13Z

spencerm commented

2026-10-19 02:50:13 +00:00

The rebuild follows the old screens where they were stricter than the old rules. Each can be vetoed. Table: docs/POLICY.md, section "Tightenings against the old build".

Only the holder of a packet edits shop data (welds, BOM, heat tags, checklist, weld record, timer); a lead of another department cannot.
Only the assigned welder starts or submits a packet; leads and supervisors still can.
Rev-mismatch approval and moving back from VISUAL review need a Clerical Supervisor (no Clerical lead group in AD).
Packets routed to Shipping can be closed and filed; only the Data Book route needs the VISUAL close first.
The data book date is Clerical or Q.C. only.
A change-order verification cannot be withdrawn once signed.
The warehouse cannot release until every BOM line not n/a is pulled or has a short on record.
A hand-made draft needs a drawing before it leaves Clerical.
Attaching a drawing by hand needs a signature.
Admin bypasses custody to fix data but follows the workflow order.

Tick the ones to keep; comment on any to change.

Plan reference: Q7 in docs/PLAN.md (open questions). Answer here; the build takes the default until then.

The rebuild follows the old screens where they were stricter than the old rules. Each can be vetoed. Table: docs/POLICY.md, section "Tightenings against the old build". - [x] Only the holder of a packet edits shop data (welds, BOM, heat tags, checklist, weld record, timer); a lead of another department cannot. - [x] Only the assigned welder starts or submits a packet; leads and supervisors still can. - [x] Rev-mismatch approval and moving back from VISUAL review need a Clerical Supervisor (no Clerical lead group in AD). - [ ] Packets routed to Shipping can be closed and filed; only the Data Book route needs the VISUAL close first. - [x] The data book date is Clerical or Q.C. only. - [x] A change-order verification cannot be withdrawn once signed. - [x] The warehouse cannot release until every BOM line not n/a is pulled or has a short on record. - [x] A hand-made draft needs a drawing before it leaves Clerical. - [x] Attaching a drawing by hand needs a signature. - [x] Admin bypasses custody to fix data but follows the workflow order. Tick the ones to keep; comment on any to change. --- Plan reference: Q7 in [docs/PLAN.md](https://gt.pescoinc.biz/spencerm/PacketStation/src/branch/main/docs/PLAN.md) (open questions). Answer here; the build takes the default until then.

spencerm added the decision: Seth label 2026-10-19 02:50:13 +00:00

SethD commented

2026-10-26 15:44:09 +00:00

i think this is good as shown

spencerm commented

2026-10-27 20:57:45 +00:00

Thanks. Everything is recorded as kept, with one row left to confirm.

The checklist has two rows unticked. The warehouse release gate is settled by your answer on issue 16 (keep it). The other one:

"Packets routed to Shipping can be closed and filed; only the Data Book route needs the VISUAL close first."

In the old build a packet routed to Shipping had no way to be filed, so it sat at complete. The rebuild lets Clerical close and file it like any other packet. Should Shipping packets be filed this way (keep), or should they stay at complete as in the old build?

Thanks. Everything is recorded as kept, with one row left to confirm. The checklist has two rows unticked. The warehouse release gate is settled by your answer on issue 16 (keep it). The other one: "Packets routed to Shipping can be closed and filed; only the Data Book route needs the VISUAL close first." In the old build a packet routed to Shipping had no way to be filed, so it sat at complete. The rebuild lets Clerical close and file it like any other packet. Should Shipping packets be filed this way (keep), or should they stay at complete as in the old build?

spencerm commented

2026-10-27 21:03:07 +00:00

Withdrawing my question above: Spencer reads "good as shown" as keeping every row, the Shipping filing row included. Recorded in docs/PLAN.md and docs/POLICY.md (PR 51). Closing.

spencerm closed this issue

2026-10-27 21:03:07 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spencerm/PacketStation#6