A filed packet does not lock the unit's ITP #25

New Issue

2026-10-19T02:50:19Z

spencerm commented

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

Built as the default: the ITP belongs to the unit, so ITP writes never look at a packet's status.

To answer: keep.

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

**Built as the default:** the ITP belongs to the unit, so ITP writes never look at a packet's status. **To answer:** keep. --- Plan reference: Q28 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 phase 6 decision: Q.C. labels 2026-10-19 02:50:19 +00:00

SethD commented

2026-10-26 14:50:53 +00:00

If the ITP is not complete, we need to block it from compiling a data book. It will need to be sent back to be completed

spencerm commented

2026-10-27 21:49:32 +00:00

Noted: a packet whose unit's ITP is not complete cannot be filed, so no data book is built until the ITP is completed. Recorded in docs/PLAN.md as change C3, to build in phase 10. Closing.

spencerm closed this issue

2026-10-27 21:49:32 +00:00

spencerm referenced this issue

2026-11-05 12:09:28 +00:00

Freeze supporting asset references at filing for deferred archive copies #63

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: spencerm/PacketStation#25