Explanation
Explanation
This section explains how devedge-sdk works and why it is shaped the way it is. Use these pages when you want to understand the reasoning behind a design decision, the security model, or the pluggability boundary — not when you need step-by-step instructions (see How-to) or API details (see Reference).
The service-authoring problems it addresses: secure, AIP-correct services without boilerplate.
How the dep-light core and adapter seam keep your service code vendor-neutral.
Fail-closed authorization, multi-tenancy enforcement, and the provable security invariants the SDK upholds.
Maintainer checklist for carving a heavy component into its own nested Go module without breaking the dep graph.
For runtime internals — the interceptor chain, codegen pipeline, and layer model — see Concepts.