Architecture and Specs

SynckHub is split into clear service boundaries.

Primary components

  • SynckHub platform (data plane APIs and item operations)
  • Common control plane (auth, tenancy, directory, snapshots)
  • Federation Clearinghouse (federation authority domain)

Contract sources

For implementation truth, start with these internal contracts:

  • SynckHub platform spec
  • SynckHub authz spec
  • Common control plane spec + OpenAPI
  • federation authority and registry specs

Design constraints to keep in mind

  • Common is not in the hot path for normal repo data operations
  • access JWTs carry identity, not full authorization decisions
  • directory and snapshot caching are required for resilience
Previous
API Guide
Next
Common API