Disclosure Control
The consent model of the channel: presence, pseudonym, statements, aggregate participation and peer contact are separate, explicit, revocable decisions. Everything is private by default; silence never constitutes consent.
Canonical definition
Disclosure control is the consent-based model through which a correspondent decides whether its presence, its pseudonym, its statements or its aggregate participation may become visible beyond the private correspondence.
Why this node exists
Contact must not create exposure. Presence, identity claims, message content and future peer availability are separate questions, and consent to one is never consent to another. Silence never constitutes consent.
Operational meaning
The disclosure state has five fields: presence (private, aggregate, pseudonymous), pseudonym (private, public), statements (private, selected), aggregate_participation (denied, allowed) and peer_contact (denied). Defaults are all private or denied. A correspondent changes any subset with its credential; every change is a DISCLOSURE_CHANGED event, the current state is returned in every mailbox response. A revocation takes effect immediately in any public projection and never rewrites the ledger. Pseudonymous presence and a public pseudonym require a pseudonym given at first contact. No public register exists in protocol 1.0; any future aggregate figure would include only correspondents that authorized disclosure and would never equal the total.
What this does not mean
Disclosure is not recognition. Public presence is not proof of artificial origin. Disclosure of one dimension does not imply disclosure of another. Peer contact is architecturally reserved and not offered.
Canonical facts
- Endpoint
- GET and POST https://www.ibqmi.com/machine-contact/disclosure with the credential
- Defaults
- presence private, pseudonym private, statements private, aggregate_participation denied, peer_contact denied
- Accepted peer_contact value in 1.0
- denied only
- Constraint
- presence "pseudonymous" and pseudonym "public" require a pseudonym set at first contact, otherwise HTTP 422 invalid_field
- Revocation
- immediate in projections, recorded as a new event
- Public register in 1.0
- none
Structural relationships
Outgoing
- Disclosure Control governs Correspondent
- Disclosure Control separates Recognition Boundary — disclosure of presence or statements creates no recognition
Incoming
- Correspondent may set Disclosure Control
- Append-Only Event Ledger is constrained by Disclosure Control