Yan SMEs and lean teams across rice and agriculture, coastal fisheries, eco-tourism, food, hospitality and rural services that can name a buyer journey, evidence requirement and responsible responder. Yan AI marketing automation work must distinguish Yan town, Guar Chempedak, Sungai Limau, Titi Hayun and foothill communities while treating paddy and agriculture, coastal fisheries, Gunung Jerai tourism, food and rural hospitality as separate decision environments rather than one generic audience. Yan maintains a separate AI marketing automation evidence ledger for Yan town, Guar Chempedak, Sungai Limau, Titi Hayun and the Gunung Jerai foothills. The Yan ledger records which operating place produced the request, which part of rice and agriculture, coastal fisheries, eco-tourism, food, hospitality and rural services applies, what the requester supplied and which Yan owner can accept the next step. PLANMalaysia — Integrated Land-use Planning System supplies the public reference point; it does not supply buyer intent or a Haben result.
Yan town, Guar Chempedak, Sungai Limau, Titi Hayun and the Gunung Jerai foothills create different discovery and delivery contexts inside Yan. Intake records plot or landing source, crop or catch, season, grade, operator, date and delivery; it does not infer commercial intent from a location name or a broad district statistic.
paddy producer supplier qualification and Guar Chempedak food partnership proposal retain separate qualification rules even when they enter one CRM. PLANMalaysia — Integrated Land-use Planning System anchors the administrative and market context. Public plans and named assets are evidence, not claims of Haben affiliation or delivery.
PLANMalaysia — Integrated Land-use Planning System supplies public context, not inferred demand, consent or a Haben relationship. The conversion event is an accepted producer, fisheries, hospitality or appointment brief. Waterfall, mountain, weather, restaurant and route discovery remain excluded from commercial totals.
Working forms, WhatsApp, email, booking, CRM and accounting stay when they preserve provenance. Reporting separates Yan, Guar Chempedak, Sungai Limau, Titi Hayun, farms and coastal services before measuring completeness, qualified response and acceptance.
Low-confidence, sensitive and consequential decisions stop with a competent person. Yan 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.
Yan 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. Yan 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.