{"slug":"platform/V2_2_RECONCILIATION_AND_INTEGRATION_RECORD_2026-08-13","title":"v2.2 Reconciliation and Integration Record","section":"platform","sectionLabel":"Platform","status":"unclassified","type":"document","path":"platform/V2_2_RECONCILIATION_AND_INTEGRATION_RECORD_2026-08-13.mdx","bytes":7985,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Integration decision record — authoritative for the v2.2 merge until superseded by a committed canonical index update.  \n**Date:** 2026-08-13  \n**Scope:** Reconcile fetched `origin/main` v2.2 (`9aa0be03`) with local IntegrateWise commits `2187bc915`, `fae942fb9`, and `bcc32af33`.  \n**Evidence boundary:** This record distinguishes implemented code/tests from normative architecture and declarations. It does not certify provider execution merely because a capability is named.\n\n## Decision summary\n\n| ID   | Decision          | Default adopted for integration                                                                                                                                                                                                             | Evidence                                                                                                             |\n| ---- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |\n| D-01 | Product core      | Adopt v2.2's One Auth → Product Package → shared runtime → projections → governed execution model, interpreted through the established Spine-first truth model.                                                                             | v2.2 §1–14; local canonical architecture and amendments.                                                             |\n| D-02 | Truth and safety  | Retain tenant/policy gates, host-owned credential authority, canonical Spine/Postgres truth, bounded operational caches, proposal/approval/action separation, and reconciliation-before-promotion.                                          | Both models agree; local implementation contracts are more specific where v2.2 is general.                           |\n| D-03 | Workbench         | Adopt capability-first, lifecycle- and context-aware Workbench projections. A hostname is a projection hint only; it is never tenant, user, role, or credential authority.                                                                  | v2.2 projection rules; local host-aware routing and Gateway CORS work.                                               |\n| D-04 | Tool capabilities | Adopt v2.2 Tool Capability contract as the target semantic contract. Mark every declared capability as `bound` only after a handler, eligibility/policy path, receipt, and reconciliation evidence are mapped.                              | v2.2 execution contract; code inspection found declarative domain bindings without corresponding handler references. |\n| D-05 | Twin              | Retain the local Silent Twin boundary: contextual, governed, inline, and non-authoritative; it can draft/propose but cannot self-approve, own credentials, or directly write canonical truth.                                               | Both models agree.                                                                                                   |\n| D-06 | Public marketing  | Retain local public/internal taxonomy: Brand Store, Book of Records, and Org Memory remain internal-only and never public marketing solution routes. Public host landings are marketing projections, not authenticated Workbench authority. | Local marketing host routing and stated product decision.                                                            |\n| D-07 | Documentation     | Import v2.2 as a normative architecture input, but do not erase local canonical evidence/amendments. The final documentation index must designate one precedence chain and list retained implementation contracts.                          | Incoming `docs/CANON.md` conflicts with local architecture index.                                                    |\n\n## Capability evidence rule\n\n`packages/workbenches` adds 18 declarative Workbench domain definitions. Their `CapabilityRef` records identify an ID, plane, governance policy, and optional provider binding. They are valuable product and UX inventory, but a declaration is not runtime proof.\n\nA capability can be described as executable only when all of the following are evidenced:\n\n1. a tenant/principal/context eligibility check;\n2. schema and connector binding validation;\n3. a Governance decision and, when required, scoped approval artifact;\n4. a bounded handler or adapter that does not expose provider credentials;\n5. an execution receipt/audit record; and\n6. reconciliation into the applicable Spine/lifecycle/continuity projection.\n\nUntil then, it is **declaration-only**. Marketing and operator UI must not imply otherwise.\n\n## Merge conflict defaults\n\n| Area                                                              | Integration default                                                                                          | Rationale                                                              |\n| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |\n| Canonical truth, tenancy, credentials, Governance, reconciliation | Preserve local doctrine and import compatible v2.2 reinforcement.                                            | These are non-negotiable safety boundaries.                            |\n| Workbench capability model and lifecycle-aware projections        | Adopt v2.2 additions where they do not bypass the local authority model.                                     | Adds explicit, useful capability-first composition.                    |\n| Host/subdomain routing                                            | Preserve local host-as-hint grammar and fail-closed origin/CORS behavior; adapt v2.2 domain registry to it.  | Prevents host-derived authority or credential forwarding.              |\n| Marketing routes and public taxonomy                              | Preserve local evidence-based public/internal taxonomy; selectively incorporate v2.2 page/content structure. | Avoids exposing internal products or overstating runtime completeness. |\n| Old duplicate docs                                                | Retain as lineage unless explicitly superseded in the final index.                                           | No history or implementation detail should disappear silently.         |\n\n## Explicitly unresolved, but non-blocking for preservation\n\n1. **Brand architecture:** whether `SpineWorkspace` becomes the external brand/primary domain or remains an implementation/category term under IntegrateWise. Until an explicit founder decision, public copy uses IntegrateWise and treats Spine as the governed context/runtime model.\n2. **Canonical filename/index:** whether v2.2 replaces `INTEGRATEWISE_ARCHITECTURE.md` outright, or the current architecture is amended and indexed as the canonical source. The integration default is a single index with both v2.2 and retained local contracts, never two competing claims.\n3. **Domain registry aliases:** v2.2 aliases such as `founderops`, `businessops`, `productengineering`, and `orgmemory` need a deliberate compatibility map before they drive URLs or public navigation.\n\n## Integration gates\n\n1. Every uncommitted source/docs/test change is independently committed or preserved by a durable Git reference.\n2. The direct-main merge has a per-conflict disposition using the defaults above.\n3. Capability declarations have an evidence matrix before any claim of live execution.\n4. Focused tests pass for imported routing, projection, and capability-contract changes.\n5. Only then create the normal merge commit and attempt a non-force push.\n"}