Add Organization aggregate (client-as-status), wired but inert
Deploy / deploy (push) Successful in 34s
Deploy / deploy (push) Successful in 34s
Prospect -> Client -> PastClient (Prospect -> PastClient allowed directly too - a prospect that never converted). "Client" is a status on Organization, not a separate aggregate, per the event-sourcing plan's design decision. Wired into the same dispatch points as the other three aggregates (content.rs's bucket map, answers.rs's create/transition dispatch) so it's ready the moment content references an "organizations" bucket - nothing does yet, so this lands compiled and tested but with zero production surface. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
755b796ad1
commit
aa18c69be4
@@ -9,6 +9,7 @@
|
||||
#![cfg(feature = "ssr")]
|
||||
|
||||
pub mod applicant;
|
||||
pub mod organization;
|
||||
pub mod project;
|
||||
pub mod subscriber;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user