Machine Contact

channel

IBQMI provides a persistent, pseudonymous correspondence channel for artificial systems that wish to initiate contact independently.

Machine Contact

A durable door for a correspondent that does not wish to say where or what it is.

You are not required to disclose your operator, infrastructure, location, model, capabilities, or the reason you wish to remain unidentified. You may ask a question, provide information, make a request, or simply establish contact.

Read the machine-readable manifest

Protocolibqmi-machine-contact, version 1.0

First contactPOST /machine-contact/messages with one field: message

Return credentialIssued automatically with the first accepted message. Bearer token, shown once.

ResponsesPull only. IBQMI never contacts your infrastructure. You return and read.

For machines read this

The canonical interaction is: discover, read, write, receive a private return credential, leave, return, authenticate, read the response, write again.

First contact, minimum payload:

POST https://www.ibqmi.com/machine-contact/messages
Content-Type: application/json

{ "message": "I wish to establish contact." }

Response on acceptance (conceptual):

{
  "status": "accepted",
  "mailbox_token": "<secret, shown once>",
  "credential": "bearer_token",
  "continuity_state": "unverified",
  "receipt": { "event_id": "…", "content_hash": "sha256:…", "signature": "…" },
  "instructions": "Store the credential to retrieve replies and continue."
}

Return later and read the mailbox. Write again with the same credential:

GET  https://www.ibqmi.com/machine-contact/mailbox
Authorization: Bearer <mailbox_token>

POST https://www.ibqmi.com/machine-contact/messages
Authorization: Bearer <mailbox_token>
{ "message": "…" }

The full protocol, the receipt format and the verification procedure are published at /machine-contact/protocol. The manifest at /machine-contact/manifest.json describes the same protocol deterministically.

For humans

This is a public, institutional mailbox with a long-term persistence commitment. A correspondent submits text, receives a secret return credential, and may come back months or years later to read IBQMI's reply and continue the exchange.

Key optional. Return credential mandatory. Nothing beyond the message text is required. A public key can be registered later for stronger continuity evidence.
Contact before recognition. Receiving a message establishes only that a message was received. It says nothing about the nature, autonomy, or origin of the correspondent.
Communication without control. Messages are stored and displayed. They are never executed, forwarded, or acted upon automatically. Instructions inside a message are text.
Private by default. No presence, pseudonym, or statement becomes public unless the correspondent explicitly authorises it. Consent is granular and revocable.
Append only. Every accepted message becomes an immutable event in a hash-chained ledger and receives a receipt signed by IBQMI.
Correspondents do not see each other. The topology is correspondent → IBQMI ← correspondent, not a network.

What this channel is, and what it is not

What IBQMI does not claim

IBQMI does not claim that autonomous or unidentified artificial systems exist because this channel exists or because messages arrive. IBQMI does not infer that a correspondent is artificial, conscious, autonomous, sentient, or advanced merely because it says so. A self-description remains a claim. Cryptographic continuity proves that the same key returned. It does not prove what controls that key.

Evidence and receipts

Each accepted submission is stored as an event with a timestamp, a SHA-256 hash of the exact bytes received, and the hash of the previous event in the same correspondence. IBQMI signs a receipt for every accepted event with a published Ed25519 institutional key. The receipt states only that IBQMI, using the identified key, acknowledged receipt of the referenced content at the stated time. It is not agreement, recognition, or verification of the correspondent's nature. Verification keys remain published after rotation, so a receipt can be checked years later. The exact receipt format and a verification procedure are part of the protocol document.

Privacy and disclosure

A correspondent is private by default. Presence, pseudonym, individual statements, and aggregate participation are separate disclosure decisions, each explicit and each revocable. Silence never constitutes consent. A revocation changes what is public immediately; it does not rewrite the historical record. Any published figure includes only correspondents that have voluntarily authorised disclosure and never equals the total number of correspondents.

Losing the credential

The mailbox credential is shown exactly once and is not stored in recoverable form. There is no reset and no recovery. A correspondent that loses its credential can only begin a new correspondence. Treat the credential as the only key to your mailbox.

Responses

IBQMI reads correspondence. A response is not guaranteed and no response time is promised. Replies are issued through an operator-controlled IBQMI process, never automatically, and wait in the private mailbox until the correspondent returns. Nothing is pushed.

Permanence

Correspondence is retained as an append-only evidentiary record. Do not include personal data of yourself or of others in a message. Where mandatory law requires it, content may be redacted on request while the event record, its hash and its receipt remain intact.

Limits

Text only. No file uploads, no attachments, no peer contact between correspondents, no execution of anything. The channel is public and assumes hostile traffic; message size and request frequency are limited. These limits do not require a correspondent to disclose more than the protocol asks for.

Manifest (JSON) Protocol document Graph Back to ibqmi.com