Reporting corporate Actions and selective Access get grouped as "servicing and disclosure." Six components make up the broader market 0 Infrastructure stack. Neither list 0 on its own tells you what a specific asset Issuer actually needs to implement.

Reporting handles retrospective audit Trails. Corporate Actions handle real time execution dividends transfers triggered as events occur. Selective access handles the disclosure Boundary deciding who sees what. All three sit within Citadel and Zedger's combined territory distinct from DuskEVM's Hedger 1 Based path entirely.

What doesn't change regardless of path chosen: an issuer implementing regulated asset workflows on Dusk is combining pieces from at least two of the six broader components identity and access through Citadel asset logic through either Zedger's or Hedger is not picking one clean self contained module.

My own read: "modulars" and "requires assembling several pieces correctly" describe the same architecture from two different angles. Neither framing is wrong. Which one a builder experiences probably depends entirely on how well the pieces actually document their own boundaries.
$NVDA.US $ACH
@Dusk_Foundation $DUSK
#dusk