{"slug":"business/01-company-and-founding-narrative","title":"01 — Company and Founding Narrative","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/01-company-and-founding-narrative.mdx","bytes":2267,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Canonical narrative; historical details require source evidence\n\n## Why IntegrateWise exists\n\nModern organisations have many specialised tools but no durable continuity\nacross them. People become the integration layer: reconstructing customer,\nproject, decision, and execution context before useful work can begin.\n\nThe founding problem is the “Human API” experience—manually bridging an\nenterprise account across Sales, Customer Success, Support, Product, Finance,\ncommunications, and delivery systems. IntegrateWise exists so people no longer\nhave to carry operational continuity in their heads.\n\n## Mission\n\nGive every person a role-specific Workbench where they and their Twin can work\nover connected organisational truth, with durable context and governed action.\n\n## Vision\n\nAn organisation should be able to connect its working systems once, preserve\noperational truth in its own Spine, and let every authorised user receive the\nminimum relevant context and capabilities for the work at hand.\n\n## Company doctrine\n\n- **Spine owns truth.** Memory can inform truth but is not truth.\n- **AI is non-authoritative.** Confidence never creates authority.\n- **Governance is a hard gate.** No approval token means no execution.\n- **The user stays in control.** Twin prepares and proposes; it does not act\n  autonomously.\n- **One surface.** The Workbench is composed by role and context rather than\n  split into architectural layers.\n- **Broad underneath, narrow at the surface.** Complexity remains in the\n  platform, not in the user's interaction model.\n\n## Company operating questions\n\nEvery initiative should answer:\n\n1. Does it reduce context reconstruction?\n2. Does it strengthen ownership, provenance, or portability of operational\n   truth?\n3. Does it make useful work easier without weakening authority boundaries?\n4. Can its end-to-end path be traced from user or platform need to verified\n   outcome?\n5. Is it demonstrably used by Customer Zero or a design partner?\n\n## Historical handling\n\nEarlier category labels, product names, and layer-based UI descriptions remain\nvaluable as evolution evidence. They must be marked Historical or Superseded and\nmust not override the frozen product definition.\n"}