Client Deployments
Client Runtime — governed AI deployment to client premises through the D1-D6 descent model.
Client Runtime
OCYL deploys governed operational intelligence directly to client premises through the Client Runtime. A standardized deployment model brings enterprise-grade capabilities to field operations — without custom development, without cloud dependency, and with full constitutional data isolation.
Every deployment follows the same structural frame. What changes is the data inside the frame, not the frame itself. Industry-specific terms appear in client instances, not in the templates.
D1-D6 Descent Model
Six phases of capability descent from the OCYL platform to client operations. Each phase builds on the previous, progressing through a 4-stage lifecycle: ORIGINATE, PROVE, PACKAGE, DESCEND.
D1: Runtime Foundation
Proven — delivered to clientCore operational frame instantiation. Templates, module types, and governance structures deployed to client environment.
- Frame instantiation
- Governance setup
- Baseline configuration
D2: Client Intelligence
Proven — delivered to clientObservation and data capture tools deployed. Operators begin capturing structured operational data during normal work.
- Flash Capture tools
- Data ingestion paths
- Observation workflows
D3: Operational Memory
Designed — not yet deployedKnowledge accumulates from operations. Registries populate with trade knowledge. The system begins remembering and retrieving.
- Knowledge registry
- Error lookup databases
- Operational history
D4: Workflows
Designed — not yet deployedAutomated workflows connect observations to actions. Repetitive tasks are identified and streamlined while maintaining operator governance.
- Workflow automation
- Operator-governed triggers
- Process optimization
D5: Dashboard
Designed — not yet deployedClient-facing operational visibility. Operators see their operational state, knowledge coverage, and system health from governed snapshot data.
- Operational visibility
- Knowledge state tracking
- Health monitoring
D6: Assistant
Designed — not yet deployedAI-assisted operations. The system provides intelligent suggestions, pattern recognition, and predictive insights — all under operator governance.
- AI-assisted decisions
- Pattern recognition
- Predictive insights
Booster Node
The Booster Node is the on-premises deployment unit. It provides local data processing, offline-capable tools, and secure integration with OCYL systems. Data stays at the client site. Intelligence flows through governed channels.
- Local data processing without cloud dependency
- Offline-capable operator tools
- Secure transfer path to OCYL systems
- Constitutional data isolation (MCA-ISO)
- Offline-capable architecture
Constitutional Isolation
Client data is constitutionally isolated. The MCA-ISO framework defines 10 rules that govern data boundaries between client environments and the OCYL platform. No client data crosses boundaries without explicit authorization. No client can access another client's data. Enterprise intelligence feeds into client environments — client data does not flow back to the enterprise without governance.
Data sovereignty is constitutional, not contractual.
Live Deployment
The Client Runtime is proven in production with a live client deployment. See the full case study for deployed tools, operational status, and deployment details.
View Case Study →Deployment Packages
Packages for businesses ready for governed operational tools.
PILOT
Client Runtime PilotPilot deployment following the proven model. D1-D2 descent with core operational tools and structured capture.
- Booster Node deployment
- Flash Capture tools
- Ongoing support
- Pilot program access
Contact us for pricing
EARLY ADOPTER
Client Runtime FullExtended Client Runtime deployment building on the proven pilot model. D1-D2 proven capabilities plus D3-D4 designed phases.
- Full Booster Node deployment
- D1-D2 proven + D3-D4 designed
- Setup + monthly support
- Early adopter program
Planned — contact us to discuss
Start Your Deployment Conversation
Interested in a Client Runtime deployment? Tell us about your operations and we will scope the right path forward.