Most systems treat verification like a memory. Pass the check once, get the stamp, and move on. That’s where things quietly break. Roles change, contexts shift, and yet old approvals keep traveling forward as if nothing happened. “Verified” becomes historical, not factual.
Dusk doesn’t work that way. Verification isn’t something you carry — it’s something the system demands at the exact moment state tries to change. Every transition asks the same question in real time: does this credential still satisfy the rule right now? If not, nothing moves. No inherited trust. No leftover permissions.
That strictness isn’t philosophical. It’s practical. Because retroactive cleanup — reversing bad transfers, unwinding compliance failures — is always more expensive than stopping the mistake at the edge. Dusk chooses enforcement over forgiveness, and for institutional systems, that’s the only sane default.
DUSK
--
--