Raub SMEs and lean teams across durian and agriculture, food processing, highland tourism, mining support, retail, logistics and hospitality that can name a buyer journey, evidence requirement and responsible responder. Raub scale with AI work must reflect town services, Sungai Ruan orchards, Tras and Cheroh communities, durian processing, highland visitor routes and rural fulfilment. Raub maintains a separate scale with AI evidence ledger for Raub town, Sungai Ruan, Tras, Cheroh and the Fraser's Hill gateway. The Raub ledger records which operating place produced the request, which part of durian and agriculture, food processing, highland tourism, mining support, retail, logistics and hospitality applies, what the requester supplied and which Raub owner can accept the next step. PLANMalaysia — Pahang Structure Plan 2050 supplies the public reference point; it does not supply buyer intent or a Haben result.
Raub town, Sungai Ruan, Tras, Cheroh and the Fraser's Hill gateway create different discovery and delivery contexts inside Raub. Produce briefs retain farm origin, variety, harvest window, grade, volume and destination; processors retain facility and authority; stays retain date and capacity.
Sungai Ruan producer supplier qualification and Fraser gateway partnership proposal retain separate qualification rules even when they enter one CRM. Pahang planning establishes Raub's agropolitan and town-growth context. Named orchards, roads and visitor destinations are not Haben relationships or promised results.
PLANMalaysia — Pahang Structure Plan 2050 supplies public context, not inferred demand, consent or a Haben relationship. Conversion is an accepted orchard, processor, hospitality or appointment brief. Fruit-price browsing, weather, road and Fraser's Hill discovery remain excluded.
Working forms, WhatsApp, email, booking, CRM and accounting stay when they preserve provenance. Measurement separates Raub town, Sungai Ruan, Tras, Cheroh, orchards, processors and highland journeys before tracking progression.
Low-confidence, sensitive and consequential decisions stop with a competent person. Raub implementation retains its existing forms, messaging, booking, CRM, finance and reporting tools where provenance and ownership remain visible. Tool replacement requires a documented control, access or integration failure.
Raub reporting keeps the operating location, required evidence, responsible owner and accepted next action visible. Broader Malaysian demand remains separate unless the team verifies that it can be served. Raub review records source dates, planning status, assumptions, consent, exceptions and approved claims. A named owner may maintain, revise or reverse the release when accepted outcomes do not improve.