Skip to content

Component Map

This is the canonical high-level component map for Oryvin.

It replaces the older split between "Component Map" and "System Component Map" so the main architectural picture is maintained in one place.

Canonical system view

flowchart TD

    subgraph Engineering
        U[Human Engineer]
        A[AI Assistance]
        U <--> A
    end

    W[WEIC<br/>Authoring and API]
    S[hg<br/>Source of Truth]
    O[Origin<br/>Source Packaging]
    X[Orchestrator<br/>Execution]
    D[DropBoxMini<br/>Artifact Distribution]
    L[Looker<br/>Validation and Screenshots]
    R[Runtime Services and Infrastructure]
    I[Identity Services<br/>Keycloak and Proxy Boundaries]

    U --> W
    A --> W

    W --> S
    S --> O
    O --> D

    X --> R
    R --> L
    L --> D

    I --> W
    I --> O
    I --> D
    I --> X
    I --> R

What the diagram means

  • WEIC → hg means governed authoring is committed to source
  • hg → Origin means Origin pulls from source rather than inventing state
  • Origin → DropBoxMini means publishable or consumable derived artifacts can be distributed from packaged source
  • Orchestrator → Runtime Services and Infrastructure means controlled execution acts on real systems
  • Runtime Services → Looker means running systems can be observed and checked
  • Looker → DropBoxMini means evidence artifacts are stored as derived outputs
  • Identity Services support protected access across the service layer

Responsibilities by component

WEIC

WEIC is the governed authoring and API platform.

It is responsible for:

  • structured documents
  • revisions and review workflows
  • publication direction
  • runtime identity through /health
  • the generation 2 move from EIC to a multi-user WildFly, Java, and PostgreSQL platform

hg

hg is the source of truth.

It is responsible for:

  • preserving authoritative source history
  • holding the baseline-bearing code and document state
  • acting as the reference point for packaging and release provenance

Origin

Origin is the source retrieval and packaging component.

It is responsible for:

  • pulling from hg
  • preparing source bundles
  • supporting controlled access to source-derived material

Origin is not the source of truth.

DropBoxMini

DropBoxMini is the artifact distribution boundary.

It is responsible for:

  • storing derived artifacts
  • serving delivery-patch, screenshot, and test-result artifacts
  • enforcing API key based access where appropriate

DropBoxMini is not a source system.

Looker

Looker is the validation and observation component.

It is responsible for:

  • loading target pages and systems
  • capturing screenshots
  • producing evidence artifacts for review and automation

Orchestrator

Orchestrator is the execution engine.

It is responsible for:

  • consuming patches
  • applying overlays
  • building
  • deploying
  • verifying runtime health
  • failing fast and reporting results

Orchestrator does not define the truth of the system. It executes controlled work against it.

Runtime Services and Infrastructure

Infrastructure provides the controlled environment where services run.

It is responsible for:

  • hosting components
  • network and proxy boundaries
  • stable execution conditions
  • supporting realistic validation

Identity Services

Identity services provide:

  • authentication
  • token issuance
  • centralized access boundaries
  • role-based access foundations

Boundary rules

The component map also defines what each component does not do.

  • WEIC is not the packaging system
  • Origin is not the source of truth
  • DropBoxMini is not the source of truth
  • Looker is not the deployment engine
  • Orchestrator is not the artifact store
  • Infrastructure is not the governed knowledge platform

Keeping these boundaries clear prevents the system from collapsing into one ambiguous tool.