{"slug":"development/contracts/communications-acp","title":"Communications & Agent Communication Contract","section":"development","sectionLabel":"Development","status":"unclassified","type":"document","path":"development/contracts/communications-acp.md","bytes":923,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: DEVELOPMENT | SOURCE: 28_COMMUNICATIONS_AND_ACP_CONTRACT.md -->\n\n# Communications & Agent Communication Contract\n\n## Bridge\n\nThe Communications Bridge carries Work-linked communication across:\n\n- Workbench chat;\n- Slack;\n- email;\n- meetings;\n- calls;\n- agent channels;\n- system events.\n\n## Semantic envelope\n\n```text\nTenant\nPrincipal\nSender\nRecipient\nWork ID\nTask ID\nPurpose\nContext Reference\nAuthority Context\nSource Channel\nCorrelation ID\nCausation ID\nProvenance\nTimestamp\n```\n\n## ACP\n\nACP = governed agent-to-agent / agent-to-Twin work handoff.\n\nIt carries:\n\n```text\nWork\nContext Reference\nCapability\nConstraints\nExpected Output\nEvidence Requirement\nResult\nStatus\nAttribution\n```\n\n## MCP\n\nMCP = tool/resource interoperability.\n\nACP and MCP are complementary, not substitutes.\n\n## Communication law\n\n> The Bridge transports Work-linked communication; it does not create authority or canonical truth.\n"}