Packet Station

Digital job packets for the PESCO shop floor. A packet moves through each department on screen instead of on paper. VISUAL releases the work and Packet Station builds the packet with the drawing from M-Files at the rev the job pull calls. Clerical checks anything flagged. Warehouse pulls parts and records heat numbers, MTRs and shorts. A supervisor assigns a station and welder. The station logs welds on the weld map, works the checklist and runs the timer. The supervisor sends it to Q.C. Q.C. inspects, accepts or rejects, and adds reports. Clerical closes the job in VISUAL, exports the manufacturing data book PDF and files it. A change in VISUAL to a packet already in the shop goes to Clerical as a change order before it reaches the shop.

This repo is the rebuild of Packet Station as a server application: Docker Compose on docker-1, PostgreSQL 16, a Python server that enforces every rule, a worker for the VISUAL feed and M-Files drawing lookups, and a React frontend as a pure client. Sign-in is PESCO's Active Directory. VISUAL is read through VisualKit and M-Files through MFilesKit, read-only.

Status

Rebuild in progress. Phase 5 done: the Supervisor and Stall screens, the weld map, the heat table, the station clock and change-order verification.

People can sign in, set up projects and units, make hand drafts, attach a drawing, and send a packet to the warehouse, a department or Q.C. The worker reads released work orders from VISUAL on a schedule, makes and updates drafts, opens change orders on packets already in the shop, looks drawings up in M-Files and attaches them at the rev VISUAL calls. Clerical sees it all on the From VISUAL panel and in the Flagged and Changes to approve columns; Admin sets the feed up on the Feed tab. Warehouse works its task board (waiting, being pulled, on hold, pulled, released), pulls parts line by line with heat numbers, shorts, receipts and MTRs, and releases to the supervisor once every line is pulled or short and every pulled line has a heat. A supervisor assigns the packet to a station and a welder, the welder starts the clock, marks welds on the drawing, places the heat table, finishes the checklist and submits with a PIN signature, and the supervisor sends it to Q.C. or routes it to another department with the marks carried. Department supervisors verify change orders with a signature. Every packet write goes through the server policy. The Q.C. screen is still a placeholder; its API exists. The old build on M:\Production\Packet Station stays the live system until go-live. The new system starts empty; nothing is migrated from M:.

Area	Exists yet?
Repo, docs, CLAUDE.md	Yes (phase 0)
Image, compose, CI, doctor, migration runner, security headers, build version endpoint	Yes (phase 0, image and stack verified on docker-1)
Sign-in (AD password, PIN on registered devices), sessions, lock screen, Account settings, Admin shell, audit, SSE	Yes (phase 1, verified against the Samba DC in the CI stack on docker-1)
Schema, policy engine, packet API, projects and units, assets, Clerical screen, packet page	Yes (phase 2, verified against PostgreSQL and the Samba DC in the CI stack on docker-1)
VISUAL feed, M-Files drawings, change orders from the feed, From VISUAL panel, Admin Feed tab and resource map	Yes (phase 3, run once against VISUAL DEV and the vault from a developer machine; fixture-driven in CI)
Warehouse screen, pull table, shorts and receipts, MTRs, release gate, upload kinds, optional ClamAV, storage alert	Yes (phase 4, verified in the CI stack on docker-1)
Supervisor and Stall screens, weld map, heat table, station clock, change-order verification	Yes (phase 5, verified in the CI stack on docker-1)
Q.C., close and file, PDFs	API only (phase 2); screens in phases 6 and 7
Project Management, Admin, notifications, backups	No (phases 8 and 9)
Regression bench and go-live	No (phase 10)

Phases

The full plan is in docs/PLAN.md.

Phase	What it delivers
0	Skeleton: repo, docs, Dockerfile, compose, CI, packetstation doctor, migration runner, headers and CSP.
1	Identity: AD sign-in, sessions, optional PIN, devices, signatures, audit, SSE, frontend shell and theme.
2	Core domain: schema, policy engine in Python, packet API, Clerical screen, packet page.
3	VISUAL feed and M-Files drawings in the worker, change orders, Clerical "From VISUAL" panel.
4	Warehouse: task board, pull table, heats, MTRs, shorts, upload pipeline.
5	Shop: supervisor and stall screens, weld map, heat table, timer, change-order verification.
6	Q.C.: inspection, accept and reject, Q.C. documents, digital ITP.
7	Close and file, HMAC seals, server-side PDFs (data book, traveler, ITP, prints, stamps).
8	Project Management screen, find bar, list view, presence.
9	Admin completion, AD reconcile, integrity job, notifications, backups and restore.
10	Regression bench, hardening, go-live and paper-fallback docs.

Folder map

CLAUDE.md  README.md  CHANGELOG.md  pyproject.toml  Dockerfile  .env.example
docs/                  the brief, the plan, security, deploy, feed, policy, schema, go-live, paper fallback
server/packetstation/  the Python package: app, worker, CLI, migrations, policy, domain, feed, drawings, PDFs
frontend/              Vite + React + TypeScript client
tests/                 server tests (pytest), e2e scenarios (Playwright), synthetic fixture generator
deploy/                compose files (base, NPM overlay, CI overlay), PostgreSQL init, Samba AD for CI
docker/                the image entrypoint
scripts/               host backup and restore scripts, systemd timer
.gitea/workflows/      CI

Not in git: .env, tests/fixtures/local/, reference/, recordings/. Real job data stays out of git and CI.

How to run

Developer machine:

python -m venv .venv
.venv\Scripts\python -m pip install -e ".[dev]"
.venv\Scripts\python -m pytest
cd frontend && npm ci && npm run build
packetstation doctor

visualkit and mfileskit install from PESCO's Gitea index with --index-url. Everything else installs from public PyPI in a separate step. See docs/DEPLOY.md.

Test stack on docker-1:

docker compose -p packetstation-test --env-file /etc/packetstation/test/stack.env \
  -f deploy/compose.yaml -f deploy/compose.proxy.yaml up -d

Phase 2 adds /api/projects, /api/units, /api/packets (header, transitions, work orders, pages, documents, BOM, shorts, welds, heat tags, heat table, stage, checklist, clock, warehouse stage, Q.C., change orders, log, seal), /api/assets and /_blob/{id}. Every packet read carries can, blocked and holder from the policy. See docs/POLICY.md and docs/SCHEMA.md.

The packetstation command has doctor, migrate, app, worker, job run <name> (one job in the foreground), fixtures use N (switch the fixture state, never on prod), ad-groups --list (the 50 AD group names the app expects) and ad-refresh (create or refresh the users from the groups' members).

Phase 3 adds the worker (packetstation worker: APScheduler, the visual-feed, drawing-lookup and housekeeping jobs, settings re-read on every fire, run now through job_requests), the VISUAL and drawing cache tables (migration 0004), /api/feed/*, /api/jobs/*, /api/admin/feed/*, rev approval and hand uploads under /api/packets/{id}, and the synthetic fixture generator (python -m tests.fixtures.generator --out DIR) that CI feeds the worker with. See docs/FEED.md.

CI stack with the Samba domain controller and the Playwright scenario, on a Docker host:

deploy/ci/make-secrets.sh
docker compose -p packetstation-ci --env-file deploy/ci/ci.env -f deploy/compose.yaml -f deploy/compose.ci.yaml up -d --build --wait
docker compose -p packetstation-ci --env-file deploy/ci/ci.env -f deploy/compose.yaml -f deploy/compose.ci.yaml --profile e2e run --rm playwright
docker compose -p packetstation-ci --env-file deploy/ci/ci.env -f deploy/compose.yaml -f deploy/compose.ci.yaml down -v

Server tests that need PostgreSQL run when TEST_PG_SUPERUSER_URL is set; the ones that need the domain controller run when the TEST_LDAP_* variables and TEST_DC_USERS_FILE are set. See deploy/samba/README.md.

Docs

• docs/BRIEF.md: the brief this rebuild follows.
• docs/PLAN.md: the approved phased plan and open questions.
• docs/SECURITY.md: old layers and where they live now, the new controls, the requirement ID table.
• docs/DEPLOY.md: host, stacks, secrets, NPM proxy host, doctor, backups.
• docs/FEED.md: the worker, the VISUAL feed, the packet rules, the fingerprint, the drawing decision table, the flags and the feed settings.
• docs/POLICY.md: who may do what, the preconditions, the order of checks, concurrency, and the tightenings against the old build.
• docs/SCHEMA.md: the database schema (phases 1 to 3).
• docs/GO-LIVE.md: go-live procedure (phase 10).
• docs/PAPER-FALLBACK.md: what the shop does when the server is down (phase 10).
• CHANGELOG.md: what changed.
• CLAUDE.md: rules for Claude Code sessions in this repo.