[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AFTXKAVCJNHGPH22975QWP":3,"skill-same:01M7AFTXKAVCJNHGPH22975QWP":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AFTXKAVCJNHGPH22975QWP","0.4.4-understand-message",null,"[0.4.4] A discrete packet of information sent over a channel, carrying a payload and metadata for routing and processi","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\u002Fmodules\u002Fenterprise_integration_patterns\u002Fskills\u002F0-4-4-understand-message\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 0.4.4-understand-message\ndescription: \"[0.4.4] A discrete packet of information sent over a channel, carrying a payload and metadata for routing and processi\"\n---\n\n# understand-message\n\n**CALL NUMBER:** `enterprise_integration_patterns.message : deep_message(9)`\n**DEFINITION:** A discrete packet of information sent over a channel, carrying a payload and metadata for routing and processing.\n\nInvoke this skill to understand `message` 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- **command_priority** (d2): A metadata field indicating the urgency or precedence level of a command message, used by schedulers and routers to order or filter command processing.\n- **command_target** (d2): The logical or physical destination endpoint to which a command message is addressed, specifying which receiver should process the invocation.\n- **command_timeout** (d2): The maximum duration a sender will wait for a command to complete before considering it failed; exceeding this triggers timeout handling or retry.\n- **execution_context** (d2): A structured record of runtime state passed alongside a command, providing the environment information needed to correctly process the operation invocation.\n- **fault_payload** (d2): A data envelope containing error details returned when an operation fails, typically including fault code, description, and optional context for recovery.\n- **idempotency_key** (d2): A unique identifier assigned to a command that allows receivers to detect and discard duplicate submissions, ensuring safe retries without double execution.\n- **operation_arguments** (d2): The parameter values supplied to the operation being invoked by a command message, structured according to the target interface's argument schema.\n- **operation_identifier** (d2): A named or coded reference that uniquely identifies which operation a command message is requesting, mapping to a procedure on the target system.\n- **result_payload** (d2): A data envelope containing the return value or outcome produced by a successfully executed operation, structured to match the expected response schema.\n- **target_interface_version** (d2): A version descriptor indicating which contract version of the target interface a command message adheres to, enabling version-aware routing and validation.\n\n### from `deep_message`\n- **dm_001** (d2): 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** (d2): semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification, and temporal context without prescribing receiver action.\n- **dm_007** (d2): document_origin: Metadata identifying the originating system, agent, or process that produced the document_message.\n- **dm_008** (d2): payload_extractor: A component that retrieves specific fields from the payload_structure for routing, correlation, or downstream transformation.\n- **dm_009** (d2): schema_registry_entry: An entry in the message_type_registry binding a business_object_type to its document_schema and authorized handlers.\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_005** (d3): content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific document instance across systems and message stores.\n- **dm_003** (d3): 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_006** (d3): processing_hint: An optional non-directive annotation suggesting preferred handling, urgency, or routing preference without constituting a command.\n\n### from `enterprise_integration_patterns`\n- **command_message** (d1): A message that encodes an invocation of an operation on the receiver, carrying method name and arguments.\n- **document_message** (d1): A message that carries a complete data payload (e.g. a purchase order) without prescribing what the receiver must do.\n- **event_message** (d1): A message that notifies the receiver something has happened, typically carrying a lightweight notification payload.\n- **guaranteed_delivery** (d1): The assurance that a message sent over a channel will eventually be delivered, even if the receiver is temporarily unavailable.\n- **message_expiration** (d1): A property on a message indicating it becomes invalid after a certain time and should be discarded if not delivered.\n- **message_historian** (d1): A component that archives all messages passing through a channel for compliance, auditing, or forensic replay.\n- **message_router** (d1): A component that inspects message content or metadata and forwards the message to one or more downstream channels.\n- **message_type_registry** (d1): A catalog that maps message type names or namespace identifiers to their schemas and handlers in the integration system.\n- **request_reply** (d1): A message exchange pattern pairing an outgoing request message with a correlated response message returned to the original sender.\n- **schema_validation** (d1): The enforcement that a message payload conforms to its declared schema before it is routed or transformed.\n- **correlation_identifier** (d2): A unique ID placed on both request and reply messages so the sender can match responses to their originating calls.\n- **dead_letter_channel** (d2): A channel where messages go after exhausting retries, signaling a delivery failure requiring intervention.\n- **idempotent_consumer** (d2): A consumer designed to safely process the same message more than once without side effects, essential for guaranteed delivery.\n- **message_store** (d2): A durable repository of all messages processed by an integration component, enabling replay and audit trails.\n- **return_address** (d2): Metadata on a reply message indicating which channel and possibly which queue the response should be routed to.\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- **at_least_once_delivery** (d2): Message delivery semantics where a message is retried until acknowledged, guaranteeing delivery but allowing possible duplicates.\n- **exactly_once_delivery** (d2): Message delivery semantics ensuring that a message is processed precisely one time, combining delivery guarantees with deduplication.\n- **content_based_router** (d2): A router that examines message payload fields to determine the destination channel, decoupling sender from destination knowledge.\n- **dynamic_router** (d2): A router that consults a registry or lookup table at runtime to determine destinations, allowing routing rules to change without redeployment.\n- **message_filter** (d2): A router that discards messages that do not meet a predicate condition, suppressing unwanted messages from downstream consumers.\n- **recipient_list** (d2): A router that sends the same message to a list of recipients computed at runtime from the message content or context.\n- **splitter** (d2): A router that breaks a composite message containing multiple items into individual messages, one per item.\n- **end_to_end_acknowledge** (d2): A correlation pattern where the final consumer sends an acknowledgment that propagates back through the routing chain to the original sender.\n- **normalizer** (d3): A transformer that reconciles multiple inbound message formats into a single canonical format before routing.\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\n\n**CALL NUMBER:** `enterprise_integration_patterns.message : deep_message(9)`\n**DEFINITION:** A discrete packet of information sent over a channel, carrying a payload and metadata for routing and processing.\n\nInvoke this skill to understand `message` 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- **command_priority** (d2): A metadata field indicating the urgency or precedence level of a command message, used by schedulers and routers to order or filter command processing.\n- **command_target** (d2): The logical or physical destination endpoint to which a command message is addressed, specifying which receiver should process the invocation.\n- **command_timeout** (d2): The maximum duration a sender will wait for a command to complete before considering it failed; exceeding this triggers timeout handling or retry.\n- **execution_context** (d2): A structured record of runtime state passed alongside a command, providing the environment information needed to correctly process the operation invocation.\n- **fault_payload** (d2): A data envelope containing error details returned when an operation fails, typically including fault code, description, and optional context for recovery.\n- **idempotency_key** (d2): A unique identifier assigned to a command that allows receivers to detect and discard duplicate submissions, ensuring safe retries without double execution.\n- **operation_arguments** (d2): The parameter values supplied to the operation being invoked by a command message, structured according to the target interface's argument schema.\n- **operation_identifier** (d2): A named or coded reference that uniquely identifies which operation a command message is requesting, mapping to a procedure on the target system.\n- **result_payload** (d2): A data envelope containing the return value or outcome produced by a successfully executed operation, structured to match the expected response schema.\n- **target_interface_version** (d2): A version descriptor indicating which contract version of the target interface a command message adheres to, enabling version-aware routing and validation.\n\n### from `deep_message`\n- **dm_001** (d2): 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** (d2): semantic_envelope: Metadata wrapper around the payload describing document provenance, intent classification, and temporal context without prescribing receiver action.\n- **dm_007** (d2): document_origin: Metadata identifying the originating system, agent, or process that produced the document_message.\n- **dm_008** (d2): payload_extractor: A component that retrieves specific fields from the payload_structure for routing, correlation, or downstream transformation.\n- **dm_009** (d2): schema_registry_entry: An entry in the message_type_registry binding a business_object_type to its document_schema and authorized handlers.\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_005** (d3): content_identifier: A stable unique reference (document_id, correlation token) that identifies this specific document instance across systems and message stores.\n- **dm_003** (d3): 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_006** (d3): processing_hint: An optional non-directive annotation suggesting preferred handling, urgency, or routing preference without constituting a command.\n\n### from `enterprise_integration_patterns`\n- **command_message** (d1): A message that encodes an invocation of an operation on the receiver, carrying method name and arguments.\n- **document_message** (d1): A message that carries a complete data payload (e.g. a purchase order) without prescribing what the receiver must do.\n- **event_message** (d1): A message that notifies the receiver something has happened, typically carrying a lightweight notification payload.\n- **guaranteed_delivery** (d1): The assurance that a message sent over a channel will eventually be delivered, even if the receiver is temporarily unavailable.\n- **message_expiration** (d1): A property on a message indicating it becomes invalid after a certain time and should be discarded if not delivered.\n- **message_historian** (d1): A component that archives all messages passing through a channel for compliance, auditing, or forensic replay.\n- **message_router** (d1): A component that inspects message content or metadata and forwards the message to one or more downstream channels.\n- **message_type_registry** (d1): A catalog that maps message type names or namespace identifiers to their schemas and handlers in the integration system.\n- **request_reply** (d1): A message exchange pattern pairing an outgoing request message with a correlated response message returned to the original sender.\n- **schema_validation** (d1): The enforcement that a message payload conforms to its declared schema before it is routed or transformed.\n- **correlation_identifier** (d2): A unique ID placed on both request and reply messages so the sender can match responses to their originating calls.\n- **dead_letter_channel** (d2): A channel where messages go after exhausting retries, signaling a delivery failure requiring intervention.\n- **idempotent_consumer** (d2): A consumer designed to safely process the same message more than once without side effects, essential for guaranteed delivery.\n- **message_store** (d2): A durable repository of all messages processed by an integration component, enabling replay and audit trails.\n- **return_address** (d2): Metadata on a reply message indicating which channel and possibly which queue the response should be routed to.\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- **at_least_once_delivery** (d2): Message delivery semantics where a message is retried until acknowledged, guaranteeing delivery but allowing possible duplicates.\n- **exactly_once_delivery** (d2): Message delivery semantics ensuring that a message is processed precisely one time, combining delivery guarantees with deduplication.\n- **content_based_router** (d2): A router that examines message payload fields to determine the destination channel, decoupling sender from destination knowledge.\n- **dynamic_router** (d2): A router that consults a registry or lookup table at runtime to determine destinations, allowing routing rules to change without redeployment.\n- **message_filter** (d2): A router that discards messages that do not meet a predicate condition, suppressing unwanted messages from downstream consumers.\n- **recipient_list** (d2): A router that sends the same message to a list of recipients computed at runtime from the message content or context.\n- **splitter** (d2): A router that breaks a composite message containing multiple items into individual messages, one per item.\n- **end_to_end_acknowledge** (d2): A correlation pattern where the final consumer sends an acknowledgment that propagates back through the routing chain to the original sender.\n- **normalizer** (d3): A transformer that reconciles multiple inbound message formats into a single canonical format before routing.\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",{"name":5,"description":7},"main","dfed66814f223a9f42bec375a3c59d74eefdcad5","kbworld\u002Fstate\u002Fmodules\u002Fenterprise_integration_patterns\u002Fskills\u002F0-4-4-understand-message","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":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sancovp\u002Fdark-factory-live --skill 0.4.4-understand-message",{"tool":38,"command":39},"bunx","bunx skills add sancovp\u002Fdark-factory-live --skill 0.4.4-understand-message",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sancovp\u002Fdark-factory-live --skill 0.4.4-understand-message","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsancovp\u002Fdark-factory-live\u002Fblob\u002Fmain\u002Fkbworld\u002Fstate\u002Fmodules\u002Fenterprise_integration_patterns\u002Fskills\u002F0-4-4-understand-message\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"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",[],[]]