All six operational domains are implemented. This page links to the canonical documentation.

Canonical Documentation

Domain	API Reference	Architecture
Configuration Promotion	Configuration Promotion API	Data Operations Architecture
Content Packages	Content Transfer (export/import)	Data Operations Architecture
Data Migrations	Migration API	Data Operations Architecture
External Importers	Importers API	Data Operations Architecture
Backups & Restore	Backups API	Data Operations Architecture
Content Sync	Content Sync API	Data Operations Architecture

Services

Service	Location	Lines
ConfigurationPromotionService	src/services/core/config-service.ts	1,066
ContentPackageService	src/services/core/content-package-service.ts	1,133
DataMigrationService	src/services/core/migration-engine.ts	984
BackupService	src/services/core/backup-service.ts	1,770
ContentSyncService	src/services/core/content-sync-service.ts	785

API Namespaces

Namespace	Handler	Routes
/api/config/*	handlers/config.ts	resources, status, export, plan, apply, history
/api/content-export/*	handlers/content-transfer.ts	validate, plan, run, jobs, download
/api/content-import/*	handlers/content-transfer.ts	validate, plan, apply, jobs
/api/migrations/*	handlers/migrations.ts	status, history, plan, apply, verify
/api/importers/*	handlers/importers.ts	sources (full routes via smart-importer plugin)
/api/backups/*	handlers/backups.ts	list, create, validate, restore-plan, restore, jobs
/api/content-sync/*	handlers/content-sync.ts	channels CRUD, plan, push, pull, jobs

Tests

File	Tests
tests/unit/services/config-service.test.ts	20
tests/unit/api/config-permissions.test.ts	24
tests/unit/services/operation-plan.test.ts	26
tests/unit/services/identity-matching.test.ts	19
tests/integration/api/config-sync.test.ts	3
Total	92

See Test Status Report for the full test coverage dashboard.

Benchmarks

• Config Promotion — tests/benchmarks/config-promotion.test.ts (297 lines)
• Content Packages — tests/benchmarks/content-package.test.ts (464 lines)

Design Principles (from original plan)

These rules are enforced in all data operation services:

• Do not keep expanding generic /api/import and /api/export.
• Do not use “sync” as a catch-all label.
• Do not move content as part of configuration promotion.
• Do not use filenames, display labels, or case-insensitive names as identity.
• Do not delete target resources in default merge mode.
• Do not export users, sessions, tokens, secrets, audit logs, or job state by default.
• Do not make data operations depend on one database adapter’s internal table names.
• Do not add heavy runtime dependencies for basic serialization, diffing, or checksums.

Related

• Data Operations Architecture — Full architecture overview with lifecycle, safety modes, and identity matching
• Configuration Promotion API — Complete API reference for /api/config/*
• Test Status Report — Current test coverage and gaps
• Roadmap 2026 — Broader project roadmap