Digital Capability Delivery

This guide is the single operating reference for the JOETEX GLOBAL digital estate. It covers what the platform does, who runs each part of it, the daily, weekly and monthly rhythms, escalation paths, release discipline and the exact steps for every buyer, grower and consumer facing workflow.

• Audience: Ops Team, Export Desk, Agronomy, Brand and Content, and the on-call technical owner.
• Digital estate: 39 live routes across six surfaces — Brand, Products, JUDE Platform, B2B Portal, CONNECT, Ecosystem Hub and this Ops portal.
• Operating principle: every public claim on the site must be traceable to a record the Ops Team can produce on request within one working day.

Standard procedure for any capability page

1. Open the engine index and confirm all six tiles render with imagery and correct codes.
2. Open each detail page; check the overview narrative, capability grid, data-flow steps and integrations still reflect reality on the estate.
3. Run the interactive tool with a realistic input set; sanity-check the output against last week's actuals.
4. Where the tool supports export, generate the PDF and confirm branding, date stamp and figures.
5. Log any drift in the Content Drift register and raise a change request to the surface owner.

1. Discovery — buyer lands via /, /products or a product detail page and downloads the line brochure (client-generated PDF).
2. Specification — buyer enters /portal and completes the three-step wizard: select lots, then Incoterm and shipping terms, then company and contact details.
3. Reference — the wizard issues an RFQ reference (format RFQ-XXXXX) and a confirmation panel. The buyer is told the desk responds within one business day.
4. Triage (Ops) — Export Desk logs the reference in the RFQ register with line, volume, Incoterm, destination port, requested window and buyer tier.
5. Availability check — cross-reference /portal/availability-desk and the JUDE yield forecast for the requested window; confirm or counter-propose.
6. Quote issue — price built from the landed-cost model in /platform/nexus-market-command; quote valid 7 days; never publish pricing on public pages.
7. Contract — repeat volumes move to a programme under /portal/contract-programmes with agreed tolerance bands.
8. Execution — consignment appears in Shipment Tracking; compliance dossier assembled per /portal/documents-compliance.
9. Close-out — provenance certificate issued from /trace; buyer performance updated in Account Intelligence.

Service levels

Grower (CONNECT)

1. Grower onboards through Farmer Enablement; profile and blocks registered in the farm twin.
2. Harvest Alerts push the window and delivery slot; grower books capacity in the app.
3. Grower Cockpit shows quality grade, volume accepted and payment status.
4. Ops reviews the outgrower modeller weekly to rebalance intake against export commitments.

Consumer (Provenance)

1. Consumer scans the pack code or visits /trace and enters a lot ID such as JTX-2847.
2. Chain of custody renders: origin block, variety, harvest date, pack house, cold-chain events, export leg.
3. Consumer or Ops downloads the branded two-page Provenance Certificate PDF.
4. Any lot that fails to resolve is logged as a P2 data incident and raised with the Compliance Officer the same day.

• All narrative and metric content lives in structured data files, one per engine, so copy changes are reviewable and reversible. Never hard-code claims into page components.
• Every metric shown publicly must have a named source and a review date. Stale metrics over 90 days are flagged at the monthly review.
• No internal financial metrics (IRR, ROI, investor returns) appear anywhere on the public site. This is a standing constraint — the site is a commercial and partnership surface, not an investment surface.
• Imagery: cinematic, botanical, light-touch. Every content image carries meaningful alt text; decorative backgrounds are marked decorative.
• Personal data: buyer contact details captured in the RFQ flow are handled under the buyer privacy commitment — collected for quotation only, retained no longer than the commercial relationship requires.

All exports are generated in the browser. If a download does not start: confirm pop-up and download blocking is off, retry once, then log a P3 with the Technical Owner including the page URL and browser.

1. Use the global search on /hub to find any tool, capability or workflow across all six zones.
2. Narrow with the kind and zone filters; results link straight to the owning zone page.
3. Apply a built-in preset such as interactive tools or carbon and sustainability for common views.
4. Save the current filter set as a named preset. Presets persist in the browser only, so each workstation maintains its own — document team-standard presets here so they can be rebuilt on a new machine.

1. All routes return 200; unknown URLs return the branded 404.
2. Zero console errors, zero broken images, zero broken internal links.
3. No horizontal overflow at 390px; layout verified at 390, 768 and 1280.
4. Every page has a unique title under 60 characters, description under 158 characters, Open Graph and canonical.
5. Exactly one h1 per page.
6. RFQ wizard completes all three steps and issues a reference.
7. One brochure, one provenance certificate and one hub simulation PDF download successfully.
8. Hub presets apply and persist across reload.
9. Product gallery: lazy-load, skeletons, keyboard navigation, swipe and lightbox all functional.
10. Sign-off recorded by the Technical Owner with date and build reference.

1. Detect — via monitoring, Ops daily check, or buyer report.
2. Triage — assign severity and owner within 15 minutes of detection.
3. Contain — take the affected surface to a safe state; hide a broken tool rather than serve wrong numbers.
4. Fix and verify — re-run the relevant regression items before declaring closure.
5. Post-incident note — cause, fix, and the check added to prevent recurrence.

• RFQ and contact submissions are not yet persisted centrally or emailed — manual handling required until backend lead capture is enabled.
• Hub saved presets are per-browser, not per-user account.
• Interactive simulators are deterministic models for illustration and commercial framing; they are decision-support, not systems of record.
• Provenance ledger entries are presentational until integrated with the live chain-of-custody source.
• Agreed next steps, in order: persist RFQs with desk notification; authenticated buyer accounts with quote history; live data feeds into the availability and tracking desks; analytics on buyer journey drop-off.