Architecture / Scout
The open UCL data plane for proving governed context.
Scout is the developer-controlled proof path: register sources, define selectors, assemble snapshots, and expose governed context through clean APIs before the enterprise deployment expands.
Core layers
How Scout is structured
01
Source registration
Describe local databases, APIs, files, and system boundaries in a repeatable data-plane model.
02
Selector execution
Create facts through deterministic mappings such as direct fields, enum conversion, thresholds, weighted scoring, and formulas.
03
Developer APIs
Expose snapshots through REST, GraphQL, admin surfaces, SDKs, webhooks, and local developer tooling.
Operating flow
The request path through the product
Source
Systems stay where they are
SQL, CRM, ERP, SharePoint, email metadata, logs, and service systems remain under customer control.
Distil
Facts gain provenance
Context facts carry confidence, freshness, source lineage, and governance attributes instead of becoming anonymous prompt text.
Serve
AI gets context, not data sprawl
Approved consumers receive the relevant context package without broad movement of raw operational data.
Governance
Boundaries the architecture must respect
Identity
Access follows enterprise roles
Fortress patterns align context access with customer identity, role boundaries, and local administration.
Audit
Evidence is first-class
Governance dashboards and export paths focus on what was read, why it was used, and which policy boundary applied.
Sovereignty
Cloud is not the raw data plane
KynticAI Cloud can manage licences, support, updates, and aggregate posture while the customer data plane owns operational data.
Integration points
Where it connects to the wider stack
Scout
Open core
Scout proves the data-plane mechanics with source registration, selectors, snapshots, and APIs.
Fortress
Enterprise deployment
Fortress adds private connectors, vaults, identity, compliance export, and customer-controlled deployment.
Elite
Operating model
Elite connects outcomes, support, updates, and the proof loop around the data-plane deployment.
Evidence boundary
What this page proves, and what it does not claim yet
Built
Local code boundary
Scout, Cloud, and Fortress repos contain the current public/core, control-plane, and enterprise runtime surfaces.
Deferred
Heavy runtime proof
Production-scale vector, model, and P99 benchmark claims remain deferred until the larger workstation is ready.