JC-26-014 — NPRA notification — AlphaMax V+ variant
Legalization Waiting externalAlphaMax V+ · Yes Global · PIC Farah Hussin
Click a stage to move the job card (mock). Steps below track progress inside the current stage.
Dossier steps
- Prepare dossier 2026-06-16
- Submit to NPRA 2026-06-24
- ! Query received — respond CURRENT —
- Approval expected — pending
job_card_steps — first not-done row is the "current" step highlighted above; each row's date is its done_at, blank while pending.
Activity diary · newest first
-
Note
Requested updated stability CoA from QC — Kevin liaising on the customer's batch documentation so we can respond to NPRA without delay.
2026-07-06 · Farah Hussin
-
Query received
NPRA queried the stability data — need updated CoA. 9 days after submission; response due within their standard window.
2026-07-03 · Farah Hussin
-
Submission
Dossier submitted to NPRA via eNOTIF portal.
2026-06-24 · Farah Hussin
-
Call
Confirmed dossier checklist with NPRA helpdesk — this is a variant notification, not a new registration, so the faster route applies.
2026-06-20 · Kevin Wong
-
Note
Opened job card — the AlphaMax V+ variant needs an NPRA notification before the Yes Global repeat-run can ship.
2026-06-16 · Farah Hussin
Entries can't be edited or deleted — this is the job card's diary. Types: Note · Call · Submission · Query received · Update.
People (PIC)
1 primary · 1 collaboratorOne primary owner + collaborators (job_card_pics pivot — is_primary flag). The primary shows in the Ops list; collaborators get the job card's notifications.
Linked records
job_cards.item_id / customer_id — at most one of item / customer / R&D request populated per card; this one carries both because the notification blocks a specific customer's shipment of a specific item.
Project Gaia — static mockup in Filament v3 idiom. No backend. Founder's worked example — appears in ops.html as the JC-26-014 row.