Split SDK into Low-Level and High-Level SDKs #218

Background

Currently, the SDK mixes low-level primitives with higher-level abstractions. This can make it harder for developers to understand the intended usage patterns and limits flexibility for advanced use cases.

Proposal

Split the SDK into two layers:

1. Low-Level SDK

   • Exposes core primitives and building blocks
   • Minimal abstractions
   • Suitable for advanced users who need fine-grained control

2. High-Level SDK

   • Built on top of the low-level SDK
   • Provides simplified APIs and common workflows
   • Designed for ease of use and rapid integration

Benefits

• Clear separation of responsibilities
• Better developer experience for both beginners and advanced users
• Easier long-term maintenance and extensibility
• Allows experimentation at the low-level layer without breaking high-level APIs

Possible Considerations

• Package structure and naming
• Backward compatibility
• Documentation explaining when to use each layer