Riaan Kleynhans
Open the engine
Operating method

Six gates: Specify · Architect · Build · Review · Ship · Operate and improve

The same engineering spine on every product. Each gate lists what it defines and the evidence this control plane holds for it today — read from state, never asserted.

Positioning

I build AI-native products for environments where trust, identity, governance and integration determine whether technology is adopted at all. I take complex solutions from specification through architecture, implementation, review and deployment on the customer's own infrastructure. Across voice, visual production, compliance, research and engineering systems, the common spine is agent orchestration, permissions, validation gates, human accountability, secure deployment and measurable acceptance criteria.

That is the same discipline I would bring to creative operations: understand the client's workflow, define the target operating model, make the commercial and technical assumptions explicit, govern AI use, and hand over a solution that can be operated and measured by the client.

Honesty proof VERIFIED on 2026-09-19 — 5 checks (typecheck, lint, tests, i18n parity, Archify doctor).

The differentiator

Not that I know AI — that I know how to make AI adoptable inside real organisations.

“Many AI projects fail because the model works but the operating environment does not. My work focuses on the operating environment: identity, data, workflow, permissions, review, integration, deployment, and measurable acceptance.”

Business alignmentRequirements disciplineTechnical architectureIntegrationIdentityGovernanceHuman accountabilityAcceptance testingSecure deploymentOperational measurement

OSDC is the client-facing solution-design application of the same engineering discipline I use across my AI-native products.

I am an AI Product & Solutions Architect who specialises in making agentic systems adoptable: I connect business objectives to workflows, architectures, identity, permissions, validation, human accountability, secure deployment and measurable outcomes. That is the capability I would bring to OLIVER's creative-operations and client-solution work.

Why this portfolio backs OSDC
Each OSDC capability, and the product evidence behind it. Click a row to go to that stage.
OSDC capability
Relevant product evidence
Digital strategy and product specification
Voinista, Viwago, Q-Intercept
Product architecture, capacity, cost and risk modelling
Vibely and workflow automation
VoiceCosmos integrations and secure deployment
VoiceIDVault, Viwago, permissions, auditability
Acceptance criteria, test-first delivery, telemetry
Platform architecture, reusable components, customer infrastructure
The eleven-stage delivery spine
Seven room sessions and four delivery stages between them — each under a gate and a NIST AI RMF function.
  1. 1AlignSpecify · Govern
  2. 2DiscoverSpecify · Map
  3. 3DiagnoseSpecify · Map
  4. 4PrioritizeArchitect · Map
  5. 5DesignBuild · Measure
  6. 6GovernBuild · Govern · delivery
  7. 7PilotShip · Measure · delivery
  8. 8DeployShip · Manage · delivery
  9. 9ProveReview · Measure
  10. 10ScaleOperate and improve · Manage
  11. 11LearnOperate and improve · Govern · delivery
One platform thesis, applied to different domains
Three layers of proof: products as evidence of the capability each layer needs.
Enterprise workflows
VoiceCosmos
Voice-native enterprise workflows
Agent orchestration, intent-to-action workflows, API integration
StudioMunich
AI visual production
Creative workflow, asset governance, human approval, production scale
Q-Intercept
Quantum readiness
Risk assessment, roadmap design, security and future-readiness
Agentic orchestration and control
Vibely
Agentic workflow execution
Multi-agent coordination, task routing, state management
Identity, evidence and memory
VoiceIDVault
Identity, voice fraud and deepfake risk
Authentication, authorization, liveness, identity governance
Viwago
Evidence-to-audit compliance
Evidence capture, validation, traceability, audit reporting
Continuum
Persistent AI coding memory
Context management, knowledge continuity, developer workflow integration
The common architecture
Each step is owned by a gate and has a place in this control plane — click to go there.
010/5 evidenced
Specify
Define Align · Diagnose
  • Business outcome
  • Users & stakeholders
  • Current process
  • Target workflow
  • Scope
  • Non-functional requirements
  • Data requirements
  • Risk classification
  • Acceptance criteria
  • Commercial assumptions
Evidence in OSDC today
Guided analysis complete (current process, users, volumes)
Requirement catalogue generated from a confirmed diagnosis
Assumptions register: 0/19 validated by a seat
Acceptance criteria agreed in the room (four tests)[ TO BE COMPLETED ]
Risk classification: 0 regulatory regime(s), 3-tier perimeter[ TO BE COMPLETED ]
021/4 evidenced
Architect
Define Model
  • System boundaries
  • Agent roles
  • Data flows
  • APIs
  • Identity
  • Permissions
  • RAG / knowledge sources
  • Human decision points
  • Failure modes
  • Monitoring
  • Deployment model
  • Security controls
Evidence in OSDC today
Verified system maps compiled in this session: 0/7 stages
Identity & permissions: 9 roles × 10 modules, default-deny
Human decision points: legal seat enrolled for Tier 3
Deployment model: client cloud (BYOK)[ TO BE COMPLETED ]
033/4 evidenced
Build
Implement Improve
  • Core workflows
  • Integrations
  • Agent tools
  • Permissions
  • User experience
  • Logging
  • Test harness
  • Configuration
  • Documentation
Evidence in OSDC today
6 agent plugins registered in the dsh runtime
SharePoint connector configured[ TO BE COMPLETED ]
Test harness green: 5 checks on 2026-09-19
Documentation: CLAUDE.md, specs, hive skills, this page
041/5 evidenced
Review
Validate Enable
  • Functional requirements
  • Security
  • Data handling
  • Prompt & model behaviour
  • Failure cases
  • Human escalation
  • Cost & latency
  • User acceptance
  • Operational readiness
Evidence in OSDC today
Honesty proof VERIFIED on 2026-09-19
Rehearsal run through: step 0/7[ TO BE COMPLETED ]
Refusals exercised in this session: 0[ TO BE COMPLETED ]
User acceptance: four tests agreed[ TO BE COMPLETED ]
Implementation-ready verdict passes
052/6 evidenced
Ship
Deploy Prove
  • On the customer's infrastructure
  • Approved keys & environments
  • With monitoring
  • With rollback
  • With runbooks
  • Ownership transferred
Evidence in OSDC today
AI compute on the client's tenant, zero retention verified[ TO BE COMPLETED ]
Keys as vault references, BYOK verified
Append-only ledgers and SIEM audit line on every action
Versioned snapshots published: 0[ TO BE COMPLETED ]
CISO checklist and connector runbook complete[ TO BE COMPLETED ]
Ownership: 0/0 seats named[ TO BE COMPLETED ]
060/5 evidenced
Operate and improve
Measure Scale
  • Adoption
  • Task completion
  • Accuracy
  • Exceptions
  • Cost
  • Latency
  • Incidents
  • Business value
  • Improvement opportunities
Evidence in OSDC today
Pilot measurements recorded: 0[ TO BE COMPLETED ]
Business value against the floor: [ TO BE COMPLETED ]
Exceptions: 3 open condition(s), 0 waived
Improvement backlog: 0 deferred condition(s) with revisit dates[ TO BE COMPLETED ]
Adoption: 0/0 seats held by named people[ TO BE COMPLETED ]