Beef COOL package preview

Livestock Ledger Exchange

A buyer-safe, audit-ready exchange surface for beef origin evidence: animal identity, lot movement, processor packet, retail COOL support, QR proof, and recall readiness without exposing private herd records.

Exchange map

One package, six evidence lanes.

The design separates what a farm records, what a processor needs, what retail can review, and what a buyer can safely see from a QR page.

01

Animal and herd identity

MIUSA UUID, QR token, farm/ranch profile, optional official ID reference, and active head-count quantity logic.

02

Origin and movement chain

Birth/place-of-raising, movement events, custody changes, processor handoff, lot split/merge, and supporting documents.

03

COOL retail review packet

Country-of-origin support packet, label review notes, package manifest, evidence links, and exception flags.

04

Processor and lot ledger

Processor event, slaughter/harvest lot, package lot, cut list, pack date, ship date, buyer/retail batch reference.

05

Buyer-safe QR proof

Public QR page shows approved origin/proof summary while private records, prices, invoices, and audit files remain protected.

06

Recall readiness

Suspect/probable/confirmed status, movement hold, product hold, traceback notes, and private official-report workflow.

Interactive preview

Ledger lane detail

Click a lane to see the preview record language and operational boundary.

Beef COOL Package Manifest

The package manifest should define package lots, origin evidence, product label claims, processing references, required attachments, and the customer-safe public proof fields.

SourceBEEF_COOL_PACKAGE_MANIFEST.md
VisibilityPrivate source, public summary
StatusPending exact intake

APAR-360 design intake

External BEEF COOL build review lane

Adam provided a VCloud package share for review. The package is received and hashed, but it is a limited APAR-362 traceability draft package rather than the complete APAR-360 static design bundle or a deployable APAR-361 Frappe app.

APAR-360BEEF COOL Certification System first-screen design and package manifest intake.
APAR-361Four-layer audit system: producer evidence, processor lot, retail review, buyer-safe QR.
APAR-36230-day / 10-step producer workflow for onboarding, evidence collection, review, and remediation.
APAR-363ERPNext DocType model, VRP API, QR verification, and future ledger readiness.
External build claimCurrent review state on a02
Static `index.html` and local assets presentNot in received package
WO and checkout files createdNot in received package
Source manifest hash capturedManifest not in received package
9 ERPNext DocType model tableNot deployable from received package
Blockchain / QR verification laneDraft events received; approval required before any claim
Source status: VCloud package received and hashed as `f046bfe7b7ad6ad8e2b588bed86d7a861c289f47d2c48ca0d21dabdd9e1e729a`. It contains `APAR-362_VRP_Blockchain_Draft.md`, `blockchain_events.json`, and `compliance_matrix.md`; it does not contain the exact `BEEF_COOL_PACKAGE_MANIFEST.md`, DocType JSONs, sample data, import scripts, or PWA implementation files needed for APAR-361 build validation.

Field preview

Core Beef COOL packet fields

These fields are a preview target for the manifest build. The exact manifest should confirm naming and required/optional state.

GroupFieldsUse
Packagepackage_id, lot_id, sku, cut_name, pack_date, net_weight, case_countConnect retail package to processor lot and buyer-safe proof.
Originfarm_id, ranch_name, birth_country, raised_country, harvest_country, product_of_claimSeparate evidence from claim language for COOL/Product of USA review.
Custodyanimal_uuid, movement_event, processor_id, processing_date, shipment_idPreserve chain events without exposing private documents publicly.
Evidencemanifest_hash, document_set, reviewer_status, exception_flags, receipt_hashSupport audit review and future attestation without claiming a seal before evidence exists.
Public QRqr_token, buyer_safe_status, approved_claim_summary, recall_tierShow only approved public fields and hide private farm/process/payment records.

Recall MGT

Screwworm notification and alerting lane

This lane connects Livestock Ledger package events to the existing VRP Cattle Recall Alert workflow. It is a validation and alert-routing design until approved notification recipients and test-send gates are complete.

New World Screwworm readiness

Live ERP recall readiness already supports `New World Screwworm` as a hazard type, with recall tiers `suspect`, `probable`, and `confirmed`. The preview design routes package/animal/lot events into Recall MGT while keeping private evidence protected.

DoctypeVRP Cattle Recall Alert
Public QRBuyer-safe tier only
Send StatusApproval gated
1. TriggerAnimal, package lot, processor, buyer hold, label claim hold, or screwworm hazard intake.
2. ValidateOperator verifies evidence, jurisdiction, external case reference, and action required.
3. NotifyDraft notification prepared for internal review; no live send until approved test gate.
4. Publish tierPublic QR receives only buyer-safe recall tier/status after review.

Validation matrix

Compliance boundary requirements

Every requirement must pass before this becomes a live customer workflow.

RequirementValidation/TestStatus
Evidence organization onlyPage and API copy must state workflow support, not certification.Preview Pass
No Product of USA or COOL certification claimPublic language must say evidence support and review, not certified/approved.Preview Pass
No USDA/FSIS/APHIS replacementBoundary text must preserve regulatory and veterinary obligations.Preview Pass
No legal advicePage must avoid legal conclusions and route final decisions to qualified advisors/regulators.Preview Pass
No ledger/TPM/blockchain attestation claimReceipts remain draft/evidence-bound until matching evidence and approval exist.Preview Pass
Recall MGT installedLive API reports `VRP Cattle Recall Alert` available.Live Readback Pass
Screwworm hazard supportedLive API hazard list includes `New World Screwworm`.Live Readback Pass
Notification and alertingDefine recipients, draft copy, test-send account, opt-in/authority boundaries, and approval gate.Next Build Gate
Exact BEEF COOL manifestHash and parse `BEEF_COOL_PACKAGE_MANIFEST.md` after intake.Source Pending
Compliance boundary: This preview supports evidence organization and workflow design. It does not certify a Product of USA or COOL claim, does not replace USDA/FSIS/APHIS requirements, does not provide legal advice, and does not create a ledger/TPM/blockchain attestation until matching evidence and approval exist.