Answer
It points to a Git repo/path containing the child Application YAML files (or a Helm/Kustomize setup that renders them). When synced, ArgoCD applies those Application resources into the argocd namespace, and each child then syncs its own workloads from its own source.
Real-world example The parent's path is 'clusters/prod/apps', a directory of Application manifests that become the prod cluster's apps.