{"slug":"strategy/business-strategy/52-roadmap","title":"Roadmap","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/52-roadmap.mdx","bytes":2167,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nThis page captures the current platform progress and likely near-term direction from canonical docs. It is not a marketing commitment timeline.\n\nFor canonical state, see:\n\n- `docs/CANONICAL_STATE.md`\n- `docs/README.md`\n- `docs/architecture/PRODUCT_ARCHITECTURE.md`\n- `docs/spec/INTEGRATEWISE_CANONICAL_SPEC_v1.0.md`\n\n## Platform maturity themes\n\n- L0 onboarding and tenant hydration are solid for Customer Zero.\n- L1 Workbench is the primary operational surface with domain-aware projections.\n- L2, L3, L4 surfaces are functional and continue to mature.\n- Governance, approvals, audit, and execution surfaces are active inside Customer Zero.\n- Handoff layer, outcome ingestion, and external customer dispatch flows are targeted and advancing.\n\n## External customer priorities\n\n- Approval Center and Handoff Layer remain major external customer enablers.\n- Adapter implementations for JSON, MCP, Hermes, OpenClaw, n8n, and other targets need completion.\n- Outcome ingestion webhook contracts need stabilized implementation.\n- Async state machine behavior needs consistent operator and partner documentation.\n\n## Architectural guardrails for roadmap items\n\nAny new capability must preserve:\n\n- Workbench-first composition.\n- four-button interaction grammar.\n- four distinct connection paths.\n- hard separation between Activation Bridge and Continuity Bridge.\n- Creamy, Delta, and Streaming Load semantics.\n- Spine Networking as governed context topology, not an ESB.\n- state ownership boundaries.\n- two-gate governance.\n- ExecutionPlan as the approval target.\n- promotion as the only path to canonical truth after execution.\n\n## Documentation direction\n\nThis docs site should grow with:\n\n- API versioning and breaking-change policy\n- example handoff contracts per adapter target\n- partner integration tests and verification scripts\n- partner SLA and escalation guidance\n- tenant isolation best practices for SaaS builders\n- organization readiness criteria before enabling writeback or execution paths\n\nDo not add roadmap claims that contradict canonical state. If a capability is marked as target or partial in canon, this roadmap should reflect that state.\n"}