## Author & Acknowledgment
This project was developed by the repository owner.
An AI-based assistant was used as a learning and productivity support tool
to refine the project structure, improve code quality, and align the solution
with regulatory and audit-oriented best practices.
## Integration with Data Integrity (ALCOA+)
This project is designed to operate **after data integrity validation**.
Before executing any traceability analysis or mock recall, datasets
(e.g. production, batches, shipments) should be validated against
**ALCOA+ data integrity principles** to ensure they are:
- Attributable
- Legible
- Contemporaneous
- Original
- Accurate
- Complete
- Consistent
- Enduring
- Available
An external **ALCOA+ Checker** can be used as a validation gate.
If critical data integrity violations are detected, the mock recall
should not be executed, as traceability results would not be reliable.
This separation reflects real-world QA system design, where data
integrity validation and operational analytics are independent but
logically connected processes.
## Example Workflow
1. Execute ALCOA+ data integrity checks on operational datasets
2. Review and resolve any critical violations
3. Approve datasets for operational use
4. Execute batch traceability and mock recall
5. Generate recall evidence and KPIs
Metadata
Release files for batch-traceability-mock-recall 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| batch_traceability_mock_recall-0.1.1.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| batch_traceability_mock_recall-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.9 kB
Release files / batch_traceability_mock_recall-0.1.1.tar.gz
| Download URL | batch_traceability_mock_recall-0.1.1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1859e452abd23a5411fb3fffe9a09a507ffcb1e089fc22cbb6f86ff5ac73842
|
|
BLAKE2b-256 checksum How to use checksums |
b6bcaee15b9ac43a624b181c26a80ff657e6e0f3df34c90f6db532b02c380ebc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / batch_traceability_mock_recall-0.1.1-py3-none-any.whl
| Download URL | batch_traceability_mock_recall-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
471fecb67e8f3f232e9f3473a59664702ce893383a666fdcbf716675e2ee9556
|
|
BLAKE2b-256 checksum How to use checksums |
fa9240991b201cf4ec5835d26b5d8732b88e2b495fb69a1a178125fb5d54247c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for batch-traceability-mock-recall 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.