[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AE8Z13F3AMRCTD62R8MR91":3,"skill-same:01M7AE8Z13F3AMRCTD62R8MR91":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":28,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AE8Z13F3AMRCTD62R8MR91","0.4.2-understand-message_channel",null,"sancovp\u002Fdark-factory-live","sancovp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F147458096?v=4","01M74F2EFE4Q0KF1Y5AY27HVNB","Isaac Wostrel-Rubin","01M7AC3EB8VZXS1SKHQW1EZ4N1",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Fenterprise_integration_patterns\u002Funderstand-enterprise_integration_patterns\u002Funderstand-message_channel\u002F.claude\u002Fskills\u002F0.4.2-understand-message_channel\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 0.4.2-understand-message_channel\ndescription: [0.4.2] A virtual pipeline through which messages travel from sender to receiver; analogous to a typed stream or queue\n---\n\n# understand-message_channel\n\n**CALL NUMBER:** `enterprise_integration_patterns.message_channel : deep_message(6), deep_message_channel(1)`\n**DEFINITION:** A virtual pipeline through which messages travel from sender to receiver; analogous to a typed stream or queue.\n\nInvoke 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\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **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.\n\n### from `deep_message`\n- **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.\n- **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.\n- **dm_002** (d4): semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification, and temporal context without prescribing receiver action.\n- **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.\n- **dm_005** (d5): content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific document instance across systems and message stores.\n- **dm_006** (d5): processing_hint: An optional non-directive annotation suggesting preferred handling, urgency, or routing preference without constituting a command.\n\n### from `deep_message_channel`\n- **untyped_channel** (d2): A channel without a declared datatype that accepts messages of any type, serving as the contrast to datatype channels.\n\n### from `enterprise_integration_patterns`\n- **channel_adapter** (d1): A connector that bridges external systems or protocols into a messaging channel, encapsulating the legacy system's API.\n- **channel_purger** (d1): A system management pattern that periodically clears a channel of stale or poison messages to reset system state.\n- **datatype_channel** (d1): A channel dedicated to one message type, enforcing contract clarity at the channel level rather than inside the payload.\n- **dead_letter_channel** (d1): A channel where messages go after exhausting retries, signaling a delivery failure requiring intervention.\n- **detour** (d1): A system management pattern that reroutes messages through a debugging or inspection step before resuming normal delivery.\n- **health_check_endpoint** (d1): A monitoring interface that exposes integration component status (channels healthy, queues depth, processing lag) for observability.\n- **invalid_message_channel** (d1): A channel that captures malformed or unprocessable messages for manual inspection instead of blocking the main flow.\n- **point_to_point_channel** (d1): A channel with exactly one consumer per message; guarantees that exactly one receiver processes each message.\n- **polling_consumer** (d1): A consumer that repeatedly queries a source for new messages rather than receiving them push-style from a channel.\n- **publish_subscribe_channel** (d1): A channel where one publisher sends and all subscribed receivers consume; each gets its own copy of the message.\n- **test_message** (d1): A system management pattern that injects a known probe message into the flow to verify correct processing downstream.\n- **wire_tap** (d1): A system management pattern that taps into a channel to observe messages without disrupting the normal flow.\n- **messaging_gateway** (d2): A Façade that exposes integration functionality to internal clients while hiding the underlying messaging API and complexity.\n- **durable_subscriber** (d2): A subscriber registration that survives broker restarts; undelivered messages are queued and delivered once the subscriber reconnects.\n- **event_subscription** (d2): The registration of a consumer's interest in receiving messages from a particular channel or topic based on content or type.\n- **list_of_interceptors** (d2): A system management pattern that registers interceptor objects to run before or after message processing for cross-cutting concerns.\n\n## CONSUMERS (what needs this)\n`datatype_channel`, `messaging_system`, `untyped_channel`\n\n---\n*Projected from the `enterprise integration patterns` KB (154 concepts \u002F 176 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n","# understand-message_channel\n\n**CALL NUMBER:** `enterprise_integration_patterns.message_channel : deep_message(6), deep_message_channel(1)`\n**DEFINITION:** A virtual pipeline through which messages travel from sender to receiver; analogous to a typed stream or queue.\n\nInvoke 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\u002FSWI-Prolog consistency gate): every reference below resolves.\n\n## THE RELATIVE ROOT (the import cone, by lib)\n\n### from `?`\n- **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.\n\n### from `deep_message`\n- **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.\n- **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.\n- **dm_002** (d4): semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification, and temporal context without prescribing receiver action.\n- **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.\n- **dm_005** (d5): content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific document instance across systems and message stores.\n- **dm_006** (d5): processing_hint: An optional non-directive annotation suggesting preferred handling, urgency, or routing preference without constituting a command.\n\n### from `deep_message_channel`\n- **untyped_channel** (d2): A channel without a declared datatype that accepts messages of any type, serving as the contrast to datatype channels.\n\n### from `enterprise_integration_patterns`\n- **channel_adapter** (d1): A connector that bridges external systems or protocols into a messaging channel, encapsulating the legacy system's API.\n- **channel_purger** (d1): A system management pattern that periodically clears a channel of stale or poison messages to reset system state.\n- **datatype_channel** (d1): A channel dedicated to one message type, enforcing contract clarity at the channel level rather than inside the payload.\n- **dead_letter_channel** (d1): A channel where messages go after exhausting retries, signaling a delivery failure requiring intervention.\n- **detour** (d1): A system management pattern that reroutes messages through a debugging or inspection step before resuming normal delivery.\n- **health_check_endpoint** (d1): A monitoring interface that exposes integration component status (channels healthy, queues depth, processing lag) for observability.\n- **invalid_message_channel** (d1): A channel that captures malformed or unprocessable messages for manual inspection instead of blocking the main flow.\n- **point_to_point_channel** (d1): A channel with exactly one consumer per message; guarantees that exactly one receiver processes each message.\n- **polling_consumer** (d1): A consumer that repeatedly queries a source for new messages rather than receiving them push-style from a channel.\n- **publish_subscribe_channel** (d1): A channel where one publisher sends and all subscribed receivers consume; each gets its own copy of the message.\n- **test_message** (d1): A system management pattern that injects a known probe message into the flow to verify correct processing downstream.\n- **wire_tap** (d1): A system management pattern that taps into a channel to observe messages without disrupting the normal flow.\n- **messaging_gateway** (d2): A Façade that exposes integration functionality to internal clients while hiding the underlying messaging API and complexity.\n- **durable_subscriber** (d2): A subscriber registration that survives broker restarts; undelivered messages are queued and delivered once the subscriber reconnects.\n- **event_subscription** (d2): The registration of a consumer's interest in receiving messages from a particular channel or topic based on content or type.\n- **list_of_interceptors** (d2): A system management pattern that registers interceptor objects to run before or after message processing for cross-cutting concerns.\n\n## CONSUMERS (what needs this)\n`datatype_channel`, `messaging_system`, `untyped_channel`\n\n---\n*Projected from the `enterprise integration patterns` KB (154 concepts \u002F 176 relations) — consistency-typed by MAP; the facet list after the colon IS the cross-lib dependency web.*\n\n_(leaf — this is an actual skill.)_\n",{},"main","dfed66814f223a9f42bec375a3c59d74eefdcad5","kbworld\u002Fstate\u002Flibraries\u002Fenterprise_integration_patterns\u002Funderstand-enterprise_integration_patterns\u002Funderstand-message_channel\u002F.claude\u002Fskills\u002F0.4.2-understand-message_channel","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live","https:\u002F\u002Fgithub.com\u002Fsancovp","https:\u002F\u002Fisaacwr.carrd.co\u002F","AKA Olivus Victory-Promise\r\n\r\nAI Agents, Tools, and Infrastructure","2026-10-09 02:22:46",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sancovp\u002Fdark-factory-live --skill 0.4.2-understand-message_channel",{"tool":37,"command":38},"bunx","bunx skills add sancovp\u002Fdark-factory-live --skill 0.4.2-understand-message_channel",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sancovp\u002Fdark-factory-live --skill 0.4.2-understand-message_channel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Flibraries\u002Fenterprise_integration_patterns\u002Funderstand-enterprise_integration_patterns\u002Funderstand-message_channel\u002F.claude\u002Fskills\u002F0.4.2-understand-message_channel\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7AGYB2CPCQYJP631CH18A1A","quests","The quest board — accept quests, craft skills to fulfill them, earn gold rewards.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fquests\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M7AGXYVW23T3X4APFAV3H4ZY","metrics","Check your profitability and trading performance — gold earned, spent, net profit, trade history.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002Fmetrics\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AGXWC0C1W7PZK5YXQW0NQM","things","Flat search across the game — find quests, knowledge domains, agents, trade listings, memories.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fthings\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AGXT9SX50REN4K7ZGE08JT","test-skill","Test a crafted skill by running it through a fresh Claude instance. Use before posting to trade or submitting for quests.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Ftest_skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AGXRA67MFHJJNDEVX6PFKR","remember","Your zettelkasten — persistent memory that survives across seasons. Record observations, strategies, and craft insights.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fremember\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AGXNND02SYFXB1JV9YRPAN","skill-types","The type system — Template, Lens, Prosthesis, Towering, Combiner, Persona, Recipe. Learn to type skills, chain them, and write Recipes.","https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fworld\u002Fagents\u002Fagent_002\u002F.claude\u002Fskills\u002Fplaces\u002Fskill_types\u002FSKILL.md",[],[]]