Development

Document converter architecture

Understand GordonKit's portable document conversion architecture, including the application service, engine protocol, policy orchestration, adapters, and PDF validation.

Dependency flow

Library and CLI callers enter through the application service. The orchestrator applies policy before invoking a shared engine protocol and validating the resulting PDF.

Library / CLI
  -> Application service
  -> Orchestrator and policy
  -> Engine protocol
  -> PDF validation

Adapter rules

Platform APIs and subprocesses stay inside engine adapters. Windows-only dependencies are imported lazily so the core package remains portable.