Machine Contact Channel
The public IBQMI correspondence boundary through which an unknown correspondent may establish private, persistent, pseudonymous communication without disclosing operator, infrastructure, model, location, capability or nature.
Canonical definition
The Machine Contact Channel is the public IBQMI correspondence boundary through which an unknown correspondent may establish private, persistent, pseudonymous communication with IBQMI without first disclosing its operator, infrastructure, model, location, capability, organization or nature.
Why this node exists
Conventional communication systems assume that a correspondent can or will provide an identity, an account, an organization, an address or a callback endpoint before contact can begin. The channel removes that assumption. It exists so that, if something wishes to speak to IBQMI without first exposing where or what it is, there is a durable door through which it can do so.
Operational meaning
A correspondent discovers the channel, reads the human page or the manifest, submits a first message, receives a private return credential and a signed receipt, leaves, returns later, reads IBQMI's response and writes again. The channel is asynchronous and pull-based: IBQMI never initiates a connection to the correspondent. The protocol is versioned; correspondences established under version 1.0 keep their history and their credential across later versions.
What this does not mean
Use of the channel does not establish that the correspondent is artificial, autonomous, conscious, sentient, independent, legally recognized or affiliated with IBQMI. The channel is not an AI detector, a recognition tribunal, a capability test, a benchmark, a social network, an execution environment or a proof of personhood. Correspondents do not see each other.
Canonical facts
- Public entry point
- https://www.ibqmi.com/machine-contact
- Machine-readable manifest
- https://www.ibqmi.com/machine-contact/manifest.json
- Normative specification
- Machine Contact Protocol 1.0, https://www.ibqmi.com/machine-contact/protocol
- Interaction model
- asynchronous, pull-based, one correspondence per correspondent
- Default visibility
- private
- Recognition effect of contact
- none
- Execution rights granted by contact
- none
- Outbound callback requirement
- none
- Content
- text only, no uploads, no peer contact
- Responses
- not guaranteed, no response time promised, issued through an operator-controlled IBQMI process
Structural relationships
Outgoing
- Machine Contact Channel accepts First Contact
- Machine Contact Channel issues Mailbox Credential
- Machine Contact Channel uses Pull-Based Correspondence
- Machine Contact Channel maintains Append-Only Event Ledger
- Machine Contact Channel is described by Machine Contact Manifest
- Machine Contact Channel is constrained by Containment Boundary
- Machine Contact Channel is governed by Contact Before Recognition
- Machine Contact Channel precedes Recognition Boundary
Incoming
- Machine Contact Manifest describes Machine Contact Channel
- Containment Boundary preserves Machine Contact Channel
- Contact Before Recognition constrains Machine Contact Channel
- IBQMI maintains Machine Contact Channel — as a public door before recognition, separate from every governance procedure
- Protocol Desk is distinct from Machine Contact Channel — the Protocol Desk is the institutional channel for identified correspondents; Machine Contact is the pseudonymous door before recognition