AGENT SKILL

0.4.2-understand-message_channel

暂无简介

License 许可
MIT
最近更新
2026-10-09
Stars
★ 0
Forks
0

03 SKILL.md 正文

understand-message_channel

CALL NUMBER: enterprise_integration_patterns.message_channel : deep_message(6), deep_message_channel(1) DEFINITION: A virtual pipeline through which messages travel from sender to receiver; analogous to a typed stream or queue.

Invoke this skill to understand message_channel down to its primitives. The RELATIVE ROOT below is the least-fixed-point closure of everything it bundles from — the full import cone, grouped by the lib each prim comes from. Projected from a prover-typed KB (MAP/SWI-Prolog consistency gate): every reference below resolves.

THE RELATIVE ROOT (the import cone, by lib)

from ?

  • channel_bridge (d2): A connection point that joins two channel segments or a channel to an external system, enabling message flow across the boundary while preserving channel semantics.

from deep_message

  • dm_004 (d2): document_schema: A formal contract defining the expected payload_structure fields, their types, cardinality, and optionality for a given business_object_type.
  • dm_001 (d3): payload_structure: The internal data shape of a document message, comprising typed fields and nested data elements that constitute the complete business data being transmitted.
  • dm_002 (d4): semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification, and temporal context without prescribing receiver action.
  • dm_003 (d4): business_object_type: A typed classifier identifying the kind of business entity the document represents, such as purchase_order, invoice, or shipment_manifest.
  • dm_005 (d5): content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific document instance across systems and message stores.
  • dm_006 (d5): processing_hint: An optional non-directive annotation suggesting preferred handling, urgency, or routing preference without constituting a command.

from deep_message_channel

  • untyped_channel (d2): A channel without a declared datatype that accepts messages of any type, serving as the contrast to datatype channels.

from enterprise_integration_patterns

  • channel_adapter (d1): A connector that bridges external systems or protocols into a messaging channel, encapsulating the legacy system's API.
  • channel_purger (d1): A system management pattern that periodically clears a channel of stale or poison messages to reset system state.
  • datatype_channel (d1): A channel dedicated to one message type, enforcing contract clarity at the channel level rather than inside the payload.
  • dead_letter_channel (d1): A channel where messages go after exhausting retries, signaling a delivery failure requiring intervention.
  • detour (d1): A system management pattern that reroutes messages through a debugging or inspection step before resuming normal delivery.
  • health_check_endpoint (d1): A monitoring interface that exposes integration component status (channels healthy, queues depth, processing lag) for observability.
  • invalid_message_channel (d1): A channel that captures malformed or unprocessable messages for manual inspection instead of blocking the main flow.
  • point_to_point_channel (d1): A channel with exactly one consumer per message; guarantees that exactly one receiver processes each message.
  • polling_consumer (d1): A consumer that repeatedly queries a source for new messages rather than receiving them push-style from a channel.
  • publish_subscribe_channel (d1): A channel where one publisher sends and all subscribed receivers consume; each gets its own copy of the message.
  • test_message (d1): A system management pattern that injects a known probe message into the flow to verify correct processing downstream.
  • wire_tap (d1): A system management pattern that taps into a channel to observe messages without disrupting the normal flow.
  • messaging_gateway (d2): A Façade that exposes integration functionality to internal clients while hiding the underlying messaging API and complexity.
  • durable_subscriber (d2): A subscriber registration that survives broker restarts; undelivered messages are queued and delivered once the subscriber reconnects.
  • event_subscription (d2): The registration of a consumer's interest in receiving messages from a particular channel or topic based on content or type.
  • list_of_interceptors (d2): A system management pattern that registers interceptor objects to run before or after message processing for cross-cutting concerns.

CONSUMERS (what needs this)

datatype_channel, messaging_system, untyped_channel


Projected from the enterprise integration patterns KB (154 concepts / 176 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.

(leaf — this is an actual skill.)

04 同仓库更多 Skills