Unclassified
11 · Platform Execution View
The IntegrateWise runtime — how the platform executes business work end-to-end: IW One Auth → Spine Network → Ecosystems → Capability → Governance → Hermes → Outcome → Re-ingest → Spine.
How the Platform Executes Business Work
IW One Auth
↓
IW Spine Network
↓
Ecosystems
↓
Discovery (what exists / what is available?)
↓
Activation (what should become active for this tenant/runtime/context?)
↓
Capability Fabric (what can be done? — provider-neutral)
↓
Governance (may it be done? — policy → approval → authorization)
↓
Hermes (execute what has been authorized)
↓
Execution (external system)
↓
Outcome + Evidence
↓
Re-ingestion (Loader → Normalizer → Pipeline → Governed Writer)
↓
Verification (expected vs observed)
↓
Reconciliation (resolve, decide what becomes truth)
↓
Business Context Spine
↓
Projection invalidation → Human + AI Workbench rehydrate
No stage is optional for closure. The pipeline answers what can be done, governance answers may it be done, Hermes answers execute it — but only verification → reconciliation → Spine turns outcome into truth.
Stage Responsibilities
| Stage | Answers | Key contract |
|---|---|---|
| IW One Auth | Who is acting, in which tenant, with what identity? | Identity & Authority |
| Spine Network | How does context travel across nodes/tenants? | Marketplace & network spec |
| Ecosystems | Which external systems are connected, with what scopes? | Ecosystem & Integration |
| Discovery | What capabilities exist across ecosystems? | Discovery & Activation |
| Activation | What should become active for this org/runtime/context? | Same |
| Capability Fabric | What can be done, provider-neutral? | Capability Fabric |
| Governance | May it be done, by whom, under which policy? | Governance & Authority |
| Hermes | Execute the authorized plan and return evidence | Hermes Execution |
| Outcome / Evidence | What did the external system actually do? | Trace + receipts |
| Re-ingest / Verify / Reconcile | Did reality change as expected? What becomes Spine truth? | Closure |
Why This Order Is Invariant
Discovery without activation exposes unavailable routes. Capability without governance executes without authority. Hermes without verification treats provider success as truth. The pipeline is a governance and truth pipeline, not just an integration bus.
Where to Go Next
<CardGroup cols={2}>IW One Auth — organizational, user, AI, and agent identity + tenancy + delegation.
Ecosystems, connectors, APIs, webhooks, MCP, and sync.
What exists vs what should become active — Bridge, Engine, Manager.
The Work-centric view of the same flow.
</CardGroup>