Developer documentation
Compatibility and Verification Boundaries
Package targets and implementation evidence are not universal runtime or service guarantees.
SoundSync
Current integration boundaries
| Area | Boundary |
|---|---|
| HISEScript | Generated script package; no native source rebuild. Validate the project and exported plugin on the chosen HISE version. |
| Native HISE | Requires patched/rebuilt HISE and compiled exported enforcement. Check the generated compatibility tools. |
| JUCE 0.6.0 | Windows VST3 and Apple VST3/AU source targets; online startup renewal and processor-owned enforcement. |
| Custom API | Product-scoped HTTP contracts; examples and fixtures have endpoint-specific evidence. |
| Embedded storefront | Check the chosen host site, routing, customer session, and responsive journey. |
| WooCommerce / partner API | Approved relationship, provider permissions, mappings, and scoped external fulfillment. |
| Rent-to-own | Configuration/test path present; production live checkout unavailable. |
| Subscriptions | Provider and package lifecycle tests are required for the product actually shipped. |
What a documentation review establishes
This review compares public information, current source, and available developer-interface controls. It does not run every provider transaction, native host, or offline cache failure. Read endpoint-specific fixture evidence and the package release checklist before extending a claim.
A successful Test Connection checks credentials and connectivity. It is not proof of payment, customer ownership, native audio gating, tax registration, or a provider delivering every email.