Policies And Registries

Registry Files

Registry files describe repo sets, sandbox profiles, env bundles, and validation commands.

Important paths:

registry/x4-pilot-registry.yaml
registry/x4-pilot-registry.source-setup.yaml
registry/x4-registry.template.yaml

Generate a starter registry from local repo checkouts:

x4 registry init \
  --repo ~/dev/repos/app \
  --repo ~/dev/repos/api \
  --repo-set current-work \
  --output ~/dev/x4/current-work.registry.yaml \
  --install skip

Review the generated file before team use. X4 can infer repo ids, remotes, default branches, package-manager setup commands, basic test commands, env allowlists, and a metadata-only sandbox profile, but repo owners still decide the final setup/test/env/sandbox policy.

Validate a registry:

x4 registry validate --registry registry/x4-pilot-registry.yaml

Execution Model

The execution model describes control and worker infrastructure:

infra/execution/x4-execution-model.yaml

Validate and print it:

x4 remote plan --model infra/execution/x4-execution-model.yaml

Orchestration Policy

Preferred repo-local policy:

.github/x4/policy.yml

Legacy policy:

.github/code-assist/policy.yml

Commands:

x4 orchestration policy validate --repo /path/to/repo
x4 orchestration policy show --repo /path/to/repo
x4 orchestration policy migrate --repo /path/to/repo --apply
x4 orchestration policy init --repo /path/to/repo --apply

GitHub Actions Workflows

Workflow	Purpose
.github/workflows/x4-self-hosted-ci.yml	Self-hosted build/test lane for X4 CLI changes.
.github/workflows/deploy-documentation.yml	Builds documentation/ and publishes the static Docusaurus site into X4Org/X4Org.github.io:x4/ for GitHub Pages.