{"slug":"canonical/adr/ADR-2026-09-04-04-integratewise-spineworkspace-separation","title":"ADR-2026-09-04-04 — IntegrateWise and SpineWorkspace separation","section":"canonical","sectionLabel":"Canon","status":"canon","type":"adr","path":"canonical/adr/ADR-2026-09-04-04-integratewise-spineworkspace-separation.md","bytes":1662,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** ACCEPTED — 2026-09-04 (founder decisions, 31 Aug 2026 §0.3/Appendix C; restated)\n\n## Context\n\nThe platform and the product were historically conflated (\"IntegrateWise Workbench\" as the daily\nproduct name). Users buy a working environment, not infrastructure; agents and docs frequently\nused the company name as the product name, corrupting positioning and vocabulary.\n\n## Decision\n\n- **SpineWorkspace** is the product and the daily working experience (`spineworkspace.com`).\n- **IntegrateWise** is the company and the infrastructure platform (`integratewise.ai`) that\n  connects the organization's software ecosystem, preserves governed business context and\n  continuity, composes SpineWorkspace for humans and AI, and coordinates authorized execution.\n- IntegrateWise is not the daily destination for most users; it is the substrate that makes the\n  SpineWorkspace experience possible. Public-facing complexity is hidden unless the user is an\n  authorized platform operator.\n\n## Alternatives considered\n\n- One brand for company and product — rejected: it forces infrastructure vocabulary into the user\n  experience and product vocabulary into platform contracts.\n- Product named after the Spine (\"Spine DB as the product\") — rejected: the Spine is the logical\n  context substrate, not the product surface.\n\n## Consequences\n\nAll user-facing language, decks, docs and UI use SpineWorkspace; all platform/infrastructure\nlanguage uses IntegrateWise. The canonical glossary (`18-CANONICAL-GLOSSARY.md`) enforces the\ndual-domain rule (`integratewise.ai` / `spineworkspace.com`).\n"}