Technical documentation¶

This track is for implementation teams, platform maintainers, integrators, and developers. It separates stable architectural responsibilities from contracts that are published only with a reproducible Community release.

Start here¶

• Architecture explains application responsibilities, execution boundaries, and the Community/Enterprise extension direction.
• Data integration connects master, transactional, configuration, and planning data to validation and reconciliation.
• Community architecture records what becomes reproducible in the public distribution.

For field-level contracts, keys, defaults, and dependencies, continue to the data catalog. For the first executable path, use the Community planning workflow.