{"slug":"strategy/product-strategy/00-layer-model","title":"Layer model","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/product-strategy/00-layer-model.mdx","bytes":2707,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nIntegrateWise is not one undifferentiated “AI product.” It is a layered system with a deliberately narrow user-facing expression.\n\n| Layer                 | What it is                                                | What the user experiences                                                       |\n| --------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------- |\n| Experience            | The interaction promise                                   | “My work already knows its context; AI prepared the hard parts; I decide.”      |\n| Product               | The role-composed IntegrateWise User Workbench            | A calm work surface for the person’s current role and work.                     |\n| Platform              | Continuity infrastructure for connected human and AI work | Mostly invisible: it preserves context, evidence, policy, and handoffs.         |\n| Access / distribution | IW-Continuity-Bridge and approved entry points            | The same bounded continuity where a user or approved external surface needs it. |\n\n## The composition axis\n\nThe product is composed around **human work context**, not around an entity record, a conversation, or a generic AI surface:\n\n`role + department + active focus + canonical work state + authority + available capabilities = workbench`\n\nAn entity can be part of the active focus. It is never the product’s organizing abstraction on its own.\n\nThis applies to every application category: Leads, Accounts, Marketing, Product, Finance, Service, Education, Personal, and future role domains. A category may have different work objects and capability slots; it must use the same continuity contract.\n\n## Ownership boundary\n\nThe Workbench owns presentation and deliberate user interaction. The platform owns durable truth, policy, orchestration, and governed execution. IW-Continuity-Bridge owns bounded access to platform capabilities. The Twin is a contextual cognitive participant in the product; it owns none of those system authorities.\n\n## Decision rule\n\nWhen a proposal mixes layers, classify it before building it:\n\n- If it preserves or reconciles work across people, tools, and agents, it belongs to the platform.\n- If it changes what a person sees and decides while doing a role’s work, it belongs to the product.\n- If it packages platform capabilities for an approved external entry point, it belongs to access/distribution.\n- If it creates a persistent conversational destination or substitutes AI for the decision-maker, it violates the intended experience unless the user explicitly enters a deeper Ask flow.\n"}