Kaukus ID

Build an independent Rust/PostgreSQL identity platform, separately from the ZITADEL-compatible port, at /home/mathias/work/identity-platform. Use a feature-oriented modular monolith with Axum/SQLx, typed Maud views, Vite/Stimulus/custom CSS and self-hosted icons. Authoritative relational state, explicit migrations, curated transactional history and outbox; security reads must not depend on replay or asynchronous projections. Start with one shared Kaukus identity realm, reusable accounts, customer/operator organizations and independent project access/roles. Identity administration is Kaukus-internal; customers continue managing users through Kaukus, with a provisioning API to be built later. Keep business-specific meeting/voting/support permissions in Kaukus. Prove reuse through feature slices before adding generic abstractions or crate splits. No near-term production cutover; leave running ZITADEL unchanged and use only fresh synthetic fixtures.