Summary of the new relationship/role/authority foundation, the effective_from activation rule, and what it means for organizations mapping their authority model.
If I activate an Authority without setting effective_from, what timestamp is recorded? Trying to reconcile our onboarding script with the lifecycle matrix.
Sharing how we modelled procurement as a governed business function rather than a “module responsibility area”. Feedback welcome from other orgs.
Before posting “is X verified?” — assurance in CLS is evaluated per fact/relationship on evidence, provenance, authority, and corroboration. There is no single blanket verified flag.
Anyone else seeing a leaked cluster when the readiness check times out? Workaround inside.
If I call activate on an Authority in PROPOSED and never set effective_from, does the transition fail, or is a timestamp stamped for me? Our onboarding job relied on null and it broke after an update.
On activation, if effective_from is absent it is stamped with the activation instant in the same transaction; an explicit value is preserved. A PROPOSED→ACTIVE transition never completes with effective_from still null.
Same applied to Membership and RoleAssignment activation in our testing — the stamp-if-absent rule is consistent across all three.
Thanks — updating our job to stop passing null explicitly. This should be in the onboarding checklist.