sancovp/dark-factory-live

0-understand-enterprise-integration-patterns

[0] the enterprise integration patterns library — every skill a certified region of the KB; call number = home : facets

0-1-understand-core

[0.1] the core subdomain of enterprise integration patterns (11 concepts)

0-1-6-understand-channel-bridge

[0.1.6] A connection point that joins two channel segments or a channel to an external system, enabling message flow a

0-1-1-understand-command-priority

[0.1.1] A metadata field indicating the urgency or precedence level of a command message, used by schedulers and route

0-1-2-understand-command-target

[0.1.2] The logical or physical destination endpoint to which a command message is addressed, specifying which receive

0-1-3-understand-command-timeout

[0.1.3] The maximum duration a sender will wait for a command to complete before considering it failed; exceeding this

0-1-4-understand-fault-payload

[0.1.4] A data envelope containing error details returned when an operation fails, typically including fault code, des

0-1-5-understand-result-payload

[0.1.5] A data envelope containing the return value or outcome produced by a successfully executed operation, structur

0-3-understand-deep-message-channel

[0.3] the deep_message_channel subdomain of enterprise integration patterns (20 concepts)

0-3-6-understand-cp-poison-message

[0.3.6] A message that has caused repeated processing failures or is structurally unprocessable and blocks channel pro

0-3-1-understand-cp-purge-action

[0.3.1] The execution step that removes qualifying messages from the channel: permanent deletion, move to dead_letter_

0-3-4-understand-cp-purge-policy

[0.3.4] A set of rules defining which messages qualify for purging: age threshold, retry exhaustion, poison detection

0-3-3-understand-cp-purge-trigger

[0.3.3] A condition that initiates a channel purge cycle; may be time-based, count-based, or event-based such as thres

0-3-5-understand-cp-stale-message

[0.3.5] A message that has exceeded its relevance window or idle duration and no longer carries actionable data for do

0-3-2-understand-cp-threshold-condition

[0.3.2] A predicate over channel_state_snapshot values that evaluates to true when purge_trigger should fire, such as

0-2-understand-deep-message

[0.2] the deep_message subdomain of enterprise integration patterns (45 concepts)

Source text: Undetermined

0-2-1-understand-dm-001

[0.2.1] payload_structure: The internal data shape of a document message, comprising typed fields and nested data elem

0-2-2-understand-dm-002

[0.2.2] semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification,

0-2-3-understand-dm-003

[0.2.3] business_object_type: A typed classifier identifying the kind of business entity the document represents, such

0-2-4-understand-dm-004

[0.2.4] document_schema: A formal contract defining the expected payload_structure fields, their types, cardinality, a

0-2-5-understand-dm-005

[0.2.5] content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific d

0-2-6-understand-dm-007

[0.2.6] document_origin: Metadata identifying the originating system, agent, or process that produced the document_mes

0-4-understand-enterprise-integration-patterns

[0.4] the enterprise_integration_patterns subdomain of enterprise integration patterns (78 concepts)

0-4-1-understand-command-message

[0.4.1] A message that encodes an invocation of an operation on the receiver, carrying method name and arguments.

0-4-3-understand-datatype-channel

[0.4.3] A channel dedicated to one message type, enforcing contract clarity at the channel level rather than inside th

0-4-2-understand-message-channel

[0.4.2] A virtual pipeline through which messages travel from sender to receiver; analogous to a typed stream or queue

0-4-4-understand-message

[0.4.4] A discrete packet of information sent over a channel, carrying a payload and metadata for routing and processi

0-4-5-understand-message-router

[0.4.5] A component that inspects message content or metadata and forwards the message to one or more downstream chann

0-4-6-understand-request-reply

[0.4.6] A message exchange pattern pairing an outgoing request message with a correlated response message returned to

0-1-1-understand-command-priority

[0.1.1] A metadata field indicating the urgency or precedence level of a command message, used by schedulers and route

0-1-2-understand-command-target

[0.1.2] The logical or physical destination endpoint to which a command message is addressed, specifying which receive

0-1-3-understand-command-timeout

[0.1.3] The maximum duration a sender will wait for a command to complete before considering it failed; exceeding this

0-1-4-understand-fault-payload

[0.1.4] A data envelope containing error details returned when an operation fails, typically including fault code, des

0-1-5-understand-result-payload

[0.1.5] A data envelope containing the return value or outcome produced by a successfully executed operation, structur

0-1-6-understand-channel-bridge

[0.1.6] A connection point that joins two channel segments or a channel to an external system, enabling message flow a

0-1-understand-core

[0.1] the core subdomain of enterprise integration patterns (11 concepts)

0-2-1-understand-dm-001

[0.2.1] payload_structure: The internal data shape of a document message, comprising typed fields and nested data elem

0-2-2-understand-dm-002

[0.2.2] semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification,

0-2-3-understand-dm-003

[0.2.3] business_object_type: A typed classifier identifying the kind of business entity the document represents, such

0-2-4-understand-dm-004

[0.2.4] document_schema: A formal contract defining the expected payload_structure fields, their types, cardinality, a