Current State
CrateStack already provides a usable Rust-first backend slice, but it is not yet the full target architecture described in the ADR and PRD.Implemented Today
- a Rust 2024 multi-crate workspace under
cratestack/ - schema parsing and semantic validation for an initial
.cstacksubset - compile-time
include_schema!expansion into a generated full server/clientcratestack_schemamodule - SQLx-backed model delegates for
create,find_many,find_unique,update, anddelete - generated Axum model CRUD and procedure routes
- host-owned authentication through
AuthProviderand internal binding throughbind_auth(...)andbind_context(...) - generated Rust client support through both full-schema
include_schema!and client-onlyinclude_client_macro!, plus generated Dart package output - policy enforcement for the current supported model and procedure policy subset
- generated telemetry for procedure wrappers, procedure routes, and model list routes
- top-level
mixindeclarations plus model@use(...)expansion for reusable field sets
Still Narrow Or Deferred
- COSE transport remains an unimplemented envelope seam
- negotiated multi-codec routing is not complete end-to-end
- the parser still validates only an initial schema subset
- production-stable exact non-Rust selection typing is not complete
- richer exposure controls and some field-level policy features are still deferred
- the client runtime remains partially spiked rather than fully mature
Best Fit Right Now
CrateStack is currently strongest for:- internal CRUD-heavy Rust services
- teams that want one schema to drive delegates, routes, and client contracts
- services that benefit from generated policy checks and typed query builders
- CBOR-first or CBOR-aware HTTP APIs that still need JSON fallback
Read Next
../getting-started/quickstartfor a minimal setup path../guides/auth-providerfor the host auth boundary../architecture/transport-architecturefor transport design../reference/auth-support-matrixfor the current auth and policy surface