Skip to content

Oryvin Architecture

This section defines the architectural shape of the Oryvin ecosystem as it exists now and as it is being brought into a stable operating model.

The architecture is centered on a simple rule:

Source is authoritative. Artifacts are derived.

That rule drives how WEIC, hg, Origin, DropBoxMini, Looker, Orchestrator, identity services, and infrastructure cooperate.

System structure

The core architecture is described through these documents:

Identity and security

Workflow and automation

Artifact lifecycle

Evidence and traceability

Platform components

The current platform shape is:

  • WEIC - governed authoring, API, and publication direction
  • hg - source of truth
  • Origin - source retrieval and packaging
  • DropBoxMini - derived artifact distribution
  • Looker - screenshot and validation evidence capture
  • Orchestrator - execution of patch, build, deploy, and verification workflows
  • Infrastructure - controlled runtime environment
  • Identity Services - authentication and authorization foundation

Verification loop

governed authoring
        ↓
source control
        ↓
packaging / execution
        ↓
deployment
        ↓
runtime verification
        ↓
evidence capture
        ↓
governed correction

This is the operational meaning of "Oryvin builds itself, almost."

A human engineer remains in control, but more of the system can be understood, validated, and corrected through explicit contracts.

Note on merged documents

The former distinction between "Component Map" and "System Component Map" has been collapsed into a single canonical component map so the architectural overview is maintained in one place.