Skip to content

Operational Flow

This document describes the practical end-to-end operational flow of the Oryvin system.

The purpose of this flow is to transform documented engineering intent into repeatable operational change while maintaining traceability and evidence.

Overview

The working Oryvin flow is:

governed authoring in WEIC
        ↓
commit to hg
        ↓
Origin pulls and packages source
        ↓
Orchestrator applies patch, builds, deploys, and verifies
        ↓
running services expose runtime identity through /health
        ↓
Looker captures evidence
        ↓
DropBoxMini distributes derived artifacts
        ↓
documentation and source are corrected under human oversight

Intent and governed knowledge

Operational work begins with documented intent.

That intent is captured in WEIC and committed to hg, which remains the source of truth for the system.

Packaging and execution

Origin prepares source-derived bundles from hg. Orchestrator executes controlled work against real systems, including patch application, build, deploy, and verification.

Runtime verification

Services expose a common /health contract so deployment success and runtime identity can be verified directly.

Evidence capture and distribution

Looker captures screenshots and related evidence from running systems. DropBoxMini stores and serves derived artifacts such as delivery-patch, screenshot, and test-result outputs.

Human oversight

The loop is intentionally not fully autonomous. A human engineer remains responsible for design, approval, and correction while the platform increasingly supports more of its own execution and validation.