Channels

Message-Queue Channel

Kafka and AMQP consumers let an institution send decision requests over its existing message bus. Kafka is an input channel; storage remains PostgreSQL.

Message Authentication

simplified flow

on message:
    if broker bound to one organization: org = bound org
    else: verify HMAC-SHA256(api key, correlationId + body)
          invalid -> error reply, no decision
    decide (same path as REST)
    reply { verdict, score, flags, decisionId }
    on failure -> error reply (never "allow")

Profiles

The Kafka bridges run in the full deployment profile.

Same decision path

Messages are mapped to the same rule facts and recorded the same way as REST requests.

Fail closed

If a decision cannot be made or recorded, the reply is an error, not an approval.

Limits

There is no event-replay store, Parquet archive or multi-day retention on the bus.

KB Analytical Solutions Inc. // Message-Queue Channel // Describes QUORUM at code baseline e9c2cf7