The reporting date has arrived. The compliance team needs to confirm the eligibility and settlement status of a certain type of asset, but does not want to broadcast all holdings to unrelated observers. This scenario first requires separating two event timelines: one for when the asset satisfies deterministic settlement conditions, and the other for when a particular role is authorized to view the information needed for the report. Completing settlement does not mean the data must be fully disclosed; granting permission to view does not mean the settlement result changes.

Dusk’s positioning places access control, privacy, selective disclosure, and deterministic settlement side by side, which clearly shows that these two issues can be designed separately. The reporting party can obtain the proofs required to verify eligibility or status, while holders can still protect balances, amounts, or counterparty relationships. After the transaction is completed, the review record should also state the basis and scope for viewing, instead of turning a single verification into full network transparency.

When conducting product reviews, you can first list events and then list permissions. The Events section should describe when admission, transactions, settlement, and reporting occur. The Permissions section should specify which fields the issuer, holder, venue, or auditor can read. This way, the system won’t use the label “confidential” to hide gaps that cannot be reviewed, nor expand “reviewable” into opening everything to everyone. If the materials do not support automatic compliance or if not all regions have already been approved, these boundaries must be preserved.

By separating settlement facts from viewing permissions, readers can accurately understand programmable privacy: when needed, leave verifiable records; when not needed, reduce unnecessary exposure. Separating events and permissions also makes disputes easier to handle: settlement records answer whether the transaction is completed, while authorization logs answer who viewed what content and when. The two types of evidence complement each other, but cannot replace one another, and you cannot infer that one has been made public based on the other. The reporting system should also preserve explanations for revocation, scope, and intended use, so that review boundaries remain explainable and can be rechecked by the responsible party, clearly.

@Dusk $DUSK #dusk