Point One Zero Platform architecturev11 · generated viewSign in to edit
Platform Layers › L5 Integration
L5 Integration
Where this layer sits on the architecture; the client plane band to its right shows the values it reads.
L5 Integration AGENT TOOL & API CALLS ENTER HERE
The movement half, the most client-weighted layer of the seven. Left side: the connector library (pre-built Egnyte, SharePoint, Airtable, generic APIs, a P1Z asset that compounds with every engagement), sync engine, schema-mapping toolkit, pipeline templates, dead-letter handling. Right side: everything that makes it this client's.
South-facing MCP tool servers (platform as MCP client; 10 logical, ~4 physical) + API gateway; connector library, sync engine, schema-mapping toolkit, built once, reused everywhere
Source catalog, the machine-readable registry of what exists, where it lives and what access applies; agents consult it before reaching for data (populated from the plane's source-estate inventory)
Plane-side: source selection, credentials & OAuth grants, field mappings (client schema → taxonomy), sync schedules, data contracts
A missing connector is BUILT into the library and SELECTED on the plane, never as engagement code; second client needing it proves it belongs (build-twice rule)
Different failure modes than storage: a broken sync loses data loudly; monitor accordingly
Boundary test: the machinery never hardcodes a client system; every connection is a plane value.
Client-specific configuration for this layer is specified band by band in Client Delivery, C5 spec: every input with its binding key, generated artifact, and verifying check.
Component reference
South-Facing MCP Tool Servers
The platform acting as MCP client toward data: one logical server per source, permissions defined once per server.
ImplementationRoughly ten logical servers consolidated onto a few physical gateways per the cloud overlay. Tool definitions follow the published design standard; the Smart Pipe antipattern (business logic inside a connector) is the failure mode to review for.
API Gateway
The outbound path for external API calls: authentication, rate limits, retries.
ImplementationFronts market-data and external services; every outbound call is metered and traced like any tool call.
Connector Library
Pre-built source connectors that compound with every engagement.
ImplementationA P1Z asset. A missing connector is built into the library and selected on the plane, never written as engagement code; the second client needing it proves it belongs.
Sync Engine
Scheduled and event-driven data movement between sources and tenant stores.
ImplementationModes and schedules are C5 plane values; every failure dead-letters rather than disappearing.
Source Catalog
The machine-readable registry of sources: what exists, where it lives, what schema and access rules apply.
ImplementationPopulated from the C6 source-estate inventory during discovery; agents consult it before reaching for data, so navigation is configured rather than guessed.
ETL, Batch & Streaming Templates
Reusable pipeline shapes for ingestion and movement.
ImplementationInstantiated with client field mappings; executed by the data-layer machinery in L7; pattern P3 is the reference trace.
Schema-Mapping Toolkit
Translates client schemas into the platform taxonomy.
ImplementationField mappings are C5 values, versioned with the binding; drift is caught by data-contract checks, not discovered in outputs.
Dead-letter Handling
Failed items parked, alerted on, and replayable; nothing silently dropped.
ImplementationAlert routing comes from the plane; a silent drop is the Silent Start antipattern.