Standard posture
Explain that standard setup uses approved EU or international providers and does not present itself as all processing inside UAE infrastructure.
Loading AI Team page
A buyer-safe explanation of what the standard deployment does, when residency-specific work becomes Complex, and what evidence is required before a special architecture is accepted.
Buyer question
Residency questions are answered honestly before access is shared or a quote is accepted. Data residency is not always a blanket legal requirement, but it is a live procurement concern. Clear limits help buyers decide without forcing unsupported claims.
Package outcome
Residency questions are answered honestly before access is shared or a quote is accepted.
What buyers should see
Each section should be short enough for an SME owner, manager, or procurement reviewer to understand before approving access or go-live.
Explain that standard setup uses approved EU or international providers and does not present itself as all processing inside UAE infrastructure.
Route dedicated, private-cloud, strict residency, public-sector-style, or regulated requirements to Complex review before quote or go-live.
Require architecture, provider support, cost model, data map, transfer review, retention review, and legal/security signoff before special posture claims.
Artifact template
Explain standard hosting, strict-residency escalation, possible reduced scopes, evidence required for special architectures, and the claim limits buyers must understand.
Classify the requirement as preference, procurement rule, contract rule, legal requirement, public-sector-style need, or unsure.
residency_requirement
Attach the data map and state the standard EU/international provider posture without implying a special local-hosting architecture.
deployment_data_map
Route dedicated, private-cloud, all-processing-inside-UAE, or strict-residency requests to Complex review before quote or go-live.
manual_review_reason
List required provider support, data-flow, retention, transfer, backup, monitoring, cost, and legal/security evidence.
architecture_review
Record estimated setup, provider, pass-through, operating, and support impact before promising a special architecture.
pass_through_cost_policy
State exactly what can and cannot be said publicly or contractually about residency until evidence and reviewer signoff exist.
public_claim_review
At intake, before quote acceptance, before go-live, and whenever hosting posture, provider route, data class, or buyer requirement changes.
Risk handling
A package only builds trust when it also explains when AI Team should pause, escalate, re-scope, or decline instead of pushing the Agent live.
Source records
These are the implementation records and public surfaces that should remain aligned as the package becomes a dashboard, PDF, or sales handoff.
Related paths
Use these links when a buyer needs supporting context before setup review.
FAQ
These answers are intentionally practical so owner-operators can decide whether the package is ready, needs review, or should pause setup.
Residency questions are answered honestly before access is shared or a quote is accepted.
The buyer requires a dedicated environment or all-processing-inside-UAE posture. The buyer is public sector or residency-sensitive. The workflow uses sensitive, regulated, or high-risk data. A provider cannot support the requested architecture with acceptable evidence.
Use config/compliance-governance.json, src/app/uae-compliance/page.tsx, src/components/site/setup-intake-form.tsx, src/app/api/setup-intake/route.ts as the starting source records for this package.