Welcome to Qarar
Qarar documentation explains the services we support, the documents usually required, the way cases move through intake and operations, and the shared vocabulary used by customers, operators, and AI agents.
This page is the starting point. The source of truth lives in plain markdown under docs/knowledgebase, so the same content can be published on the website and fed to agent workflows without another content system.
What Qarar is
Qarar is an operating layer for government, banking, document, and relocation workflows. A customer should be able to understand what a service involves before starting, upload documents once, and track what happens next without chasing separate providers.
The platform separates structure from copy. The visual layout stays consistent, while language and market content change independently for English, Spanish, Arabic, Vietnamese, UAE, Singapore, and Spain.
Who Qarar is for
The docs are for customers checking what they need before opening a case, operators who need one operational source of truth, content editors maintaining country-specific wording, and AI agents answering questions through chat.
Three things to know first
Every service has a document path. The useful part of the knowledgebase is not marketing copy. It is the practical relationship between service scope, intake requirements, reusable documents, process status, and customer action.
Market copy is not language copy. UAE, Singapore, and Spain may have different authorities, document names, and requirements. English, Spanish, Arabic, and Vietnamese are translation layers that can be applied independently.
The folder is the product surface. Keeping the repository as markdown means customers can read it, operators can maintain it, and AI agents can retrieve it without introducing a separate CMS.
Documentation repository
The public knowledgebase mirrors the source folder. New service notes, country pages, checklists, and process guides should be added as markdown files first, then surfaced through the navigation.
docs/knowledgebase/
services/
company-formation.md
residency-visas.md
banking.md
property-purchase.md
tax-residency.md
attestation-translation.md
renewals.md
intake/
checklist-company-formation.md
checklist-residency-visas.md
checklist-banking.md
checklist-tax-residency.md
checklist-attestation-translation.md
processes/
intake.md
document-vault.md
case-tracking.md
human-escalation.md
translation-attestation.md
reference/
document-types.md
statuses.md
glossary.md
markets/
uae.md
singapore.md
spain.mdQuickstart — a first service case
A service page should make the first action obvious: what the customer is trying to do, what market applies, what documents are needed, what gates the case must pass, and what output the operator or agent should produce.
service: residency-visas
market: uae
language: en
case:
applicant: customer
goal: residency route assessment
documents:
- passport
- current visa status
- photo
- proof of address
gates:
- document completeness
- authority-route fit
- operator review
outputs:
- missing-documents list
- next customer action
- operator handoff note