Protocol Layer

Buyer Agent and Seller Agent Protocol

The protocol defines how domain-specific agents clarify inputs, publish normalized intents, request enrichment, and send match-ready payloads into a shared engine. The contract is public. The production orchestration remains private.

Lifecycle

Capture raw buyer brief or supplier capability statement.
Normalize into the public intent schema.
Request clarifications if required fields are missing.
Emit a match-ready intent bundle to the shared engine.
Receive ranked candidates, review flags, and notification suggestions.

Public Events

intent.created: raw intent accepted and normalized.
intent.clarification_requested: agent needs missing detail.
intent.ready_for_match: payload is complete enough for scoring.
match.candidate_ranked: shared engine emits a scored candidate set.
match.review_required: workflow pauses for trust or quality review.

Boundary

The public protocol does not expose production session handling, private routing prompts, live queues, or database internals from the MapleBridge app. It exists so builders can understand the shape of bilateral matching without relying on the production app implementation.