The sdk names no transport, and fixtures say what two implementations may not disagree about #8
@@ -19,7 +19,7 @@ export interface ToolDefinition {
|
||||
}
|
||||
|
||||
/**
|
||||
* The metadata that rides an event as AMQP headers (novox/hq ADR 0042). An event's identity and
|
||||
* The metadata that rides an event as message headers (novox/hq ADR 0042). An event's identity and
|
||||
* provenance live here, not in the body, so a consumer — or the broker, or an audit tool — reads
|
||||
* who/when/what without parsing the payload. An unknown `x-` header is ignored, not refused: an
|
||||
* event is observed by parties that need not all understand every header.
|
||||
|
||||
+1
-1
@@ -4,7 +4,7 @@
|
||||
// credential — just the broker's topic routing). Declared as emits/consumes on the manifest so the
|
||||
// mesh knows the event graph.
|
||||
//
|
||||
// Identity and provenance ride as AMQP headers, not in the body (novox/hq ADR 0042): a consumer —
|
||||
// Identity and provenance ride as message headers, not in the body (novox/hq ADR 0042): a consumer —
|
||||
// or the broker, or an audit tool — reads who/when/what without parsing the payload, and the body
|
||||
// is only the domain payload. This surface hides the header/exchange/queue mechanics; a module
|
||||
// names a type and a body and never sees the wire.
|
||||
|
||||
@@ -25,7 +25,7 @@ export interface Broker {
|
||||
/**
|
||||
* How a module obtains its broker. The hosting runtime sets this once; module code calls broker()
|
||||
* without knowing the concrete binding. Keeping the binding out of the sdk is deliberate — the sdk
|
||||
* carries the contract, not a specific AMQP client build.
|
||||
* carries the contract, not a specific broker client build.
|
||||
*/
|
||||
let binding: (() => Broker) | undefined;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user