{"slug":"internal/architecture/CROSS_SURFACE_RECONCILIATION_GATE_2026-08-13","title":"Cross-Surface Reconciliation Gate — 2026-08-13","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/architecture/CROSS_SURFACE_RECONCILIATION_GATE_2026-08-13.mdx","bytes":6624,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Scope:** Final semantic gate before the v2.2 integration branch is considered ready for founder review.  \n**Status:** Passed with explicitly recorded unproven boundaries and founder decisions.\n\n| Surface                         | Integrated position                                                                                                                                                                  | Evidence / constraint                                                                     | Residual boundary                                                                                                   |\n| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |\n| One Workbench / Spine           | One governed, Spine-first Workbench with contextual projections; no projection owns independent truth.                                                                               | v2.2 architecture §§6–14; local reconciliation record.                                    | Runtime acceptance must remain test-evidenced.                                                                      |\n| Flow D and A/B/C                | Connection binding/identity (Flow D) remains distinct from ingestion/normalization paths (A/B/C); no host hint grants authority.                                                     | Host grammar, proxy, CORS in `2e348b0fa`; canonical flow docs.                            | Full live connector proof needs environment-backed tests.                                                           |\n| Role/projection routing         | Role, domain, lifecycle and phase shape projections; routing is not a credential or tenant authority path.                                                                           | `entry-hosts.ts`, `entry-context.ts`, Projection Engine contracts.                        | v2.2 alias URL policy requires founder decision.                                                                    |\n| Tool capabilities               | Capabilities are explicit first-class Workbench contracts, bound by context, connector availability, policy, dry-run and approval.                                                   | v2.2 execution contract; capability matrix.                                               | Most domain entries are declaration-only until handler/receipt/reconciliation proof exists.                         |\n| Silent Twin                     | Contextual, governed, non-authoritative; it can propose but cannot self-approve, own credentials, or directly write canonical truth.                                                 | v2.2 §§7–9; reconciliation D-05.                                                          | None at doctrine level.                                                                                             |\n| MCP/plugin and platform control | MCP/plugin distribution is governed product-package/platform capability; Platform Management Console is internal operator control, not the user Workbench.                           | v2.2 §§5, 10–11.                                                                          | One real binding-to-action proof remains required.                                                                  |\n| Governance / Hermes / outcome   | Proposal → scoped approval when required → bounded execution → receipt/audit → reconciliation → lifecycle/continuity update.                                                         | v2.2 §9/13; capability evidence matrix.                                                   | Provider actions cannot be claimed live absent handler evidence.                                                    |\n| Truth / operational access      | Governed Spine/Postgres truth is canonical; D1/KV/cache/memory are bounded/reconstructable or subordinate.                                                                           | v2.2 §12; local doctrine.                                                                 | Storage binding/deployment must be re-verified before production claims.                                            |\n| Marketing / internal taxonomy   | Public marketing is separate from authenticated Workbench and platform controls. Brand Store, Book of Records, and Org Memory stay internal-only and are not public solution routes. | Source-only founder doctrine, local solution-taxonomy tests/content, reconciliation D-06. | v2.2 route/content consolidation needs browser/test validation.                                                     |\n| Cloudflare / Vercel topology    | Deployment ownership remains evidence-only: use repository topology/configuration; no provider/DNS mutation occurred in this consolidation.                                          | `docs/VERCEL_PROJECT_TOPOLOGY.md`; no deployment action.                                  | Re-verify account/project/environment ownership before deploy.                                                      |\n| Tests, claims, and decisions    | Claims follow source/test evidence; safety routing import has diff/hook validation; capability execution claims are limited by matrix.                                               | Handoff ledger, matrix, safety refs.                                                      | Isolated integration worktree still lacks a completed dependency install, so focused Vitest has not executed there. |\n\n## Explicit non-contradiction rules\n\n1. v2.2's capability-first direction strengthens, rather than replaces, Spine-first context and Governance.\n2. A public subdomain landing can express marketing context only. It never becomes an authenticated authority boundary.\n3. Tool discovery, MCP exposure, and a declared provider binding are different layers; none independently proves a live external mutation.\n4. Marketing may explain the governed product model but must not expose internal-only workbenches as public solutions or claim autonomous action.\n5. The integration branch retained v2.2 core where earlier local taxonomy/docs/projection deletions could not coexist. Preserved recovery commits and safety refs retain every original source for future selective adaptation.\n"}