The next recall
should be a
rehearsal.
One ingredient. A hundred questions.
Make your records answer them before the real thing.
A lot number is
a starting point.
Evidence is
the outcome.
Your records tell a story.
Can you follow every branch?
LotZero reconstructs the connections between ingredients, production, warehouses and shipments. Run a hypothetical recall, test what the evidence can prove, then turn the gaps into work your team can act on.
All inside Jira. With uncertainty left visible.
Follow one lotFollow the lot.
Find the blind spot.
Select a shipment. Inspect its evidence.
Then rehearse what a hold could change.
Synthetic sample · selected path from a 37-record drill
A missing destination is a finding to investigate. It is not evidence that a shipment is safe.
SIMULATION ONLYThis interactive exhibit illustrates one branch of the bundled synthetic dataset. It does not run against your inventory or create Jira issues.
ING-A19 / v1
- Product lots
- 3
- Shipments
- 4
- Evidence gaps
- 9
- Unresolved records
- 12
Fixture results,
not a performance claim.
From “what if?”
to “here’s the evidence.”
A drill your team can inspect,
save and run again.
Trace every
recorded branch.
Follow a source ingredient through transformations and shipments. Inspect the path, the quantities and the evidence behind each connection.
Test what
you can prove.
Check five explicit assertions. Find absent destinations, missing owners and incomplete origins—with counterexamples, not a reassuring average.
Rehearse
the response.
Explore hypothetical holds and quarantines at the scenario’s clock. Historical shipments stay in the impact. Missing evidence stays unknown.
Make the gaps
someone’s work.
Review suggested follow-up tasks and approve the exact Jira work to create. Save the drill, export the evidence and compare the next rehearsal.
The result is a reproducible snapshot, with reports in Markdown, JSON and CSV.
Your drill.
Your Jira.
Your call.
Useful simulations need clear limits.
So does the software that runs them.
- 01 Forge-hosted data
- Application records use Atlassian Forge storage. LotZero does not require an external database or AI provider.
- 02 Project-aware access
- Server checks use the signed-in Jira user’s permissions. Importing or resetting a dataset requires project administration.
- 03 Approval before action
- Remediation tasks are created only after explicit selection and approval. The sample on this page creates nothing.
- 04 Honest uncertainty
- Incomplete records remain visible. A simulation is not a real recall decision, food-safety assessment or regulatory certification.
A little
more clarity.
What do I need to try LotZero?
A Jira Cloud site and a site administrator to install the evaluation edition. Open LotZero from a Jira project and load the labelled synthetic dataset for your first rehearsal.
Can I use my own traceability records?
Yes. The app accepts validated JSON and its documented record_type,json CSV envelope. It does not automatically connect to your ERP or map arbitrary spreadsheet columns. Review sensitive records and your project’s access before importing.
Does a passing drill mean our products are safe?
No. Assertions test the supplied records for the configured scenario. They do not establish food safety, regulatory compliance or readiness for every real incident. Your qualified team remains responsible for operational decisions.
Will a rehearsal change my shipments or contact customers?
No. Controls in LotZero are hypothetical. The application does not operate shipment systems or send recall notices. Creating suggested Jira follow-up tasks is a separate, explicitly approved action.
Is this an Atlassian Marketplace listing?
This link installs the separate, unlicensed judge and evaluation edition. The Marketplace edition has not been submitted for review. No Marketplace approval, certification or availability is claimed.
Find the gaps.
Before they matter.
Start with synthetic records.
Leave with better questions for your team.