Ports & adapters — a simulation you can make real

The orchestrator, policy engine, intake and UI are 100% real. Every external system sits behind an interface (a port). Today each port is backed by a mock adapter that simulates the real state transitions. To go live, implement the same interface against the real API — nothing else changes.

PortMock adapter (today)Live adapter (swap in)

CloudProvider

Vends Subscription (Azure) / Account (AWS) under the right MG/OU with a baseline landing zone

Azure SDK · AWS Organizations + Control Tower

Terraform

Creates workspaces, streams a plan + apply that provisions exactly the spec's resources

Terraform Enterprise API (runs, state, Sentinel)

Harness

Pipeline creation, an app build (CI), and a canary / blue-green rollout (CD)

Harness NG API (pipelines, executions)

JFrog

Publishes the build as a versioned, scanned binary of record + Xray summary

Artifactory + Xray REST API

Policy engine

REAL — 12 rules evaluate the spec and gate the run

Same code (optionally OPA / Sentinel)

1 · Intake

48-question spec captured by the App Owner, validated against a schema.

2 · Policy gate

12 real rules run; any FAIL blocks provisioning until the spec is fixed.

3 · Approve

A Platform Engineer approves; the orchestrator kicks off the run.

4 · Tenancy

Subscription / Account vended per cloud × environment with a baseline.

5 · Terraform

Workspaces created; plan + apply provision the resources the spec implies.

6 · Build → JFrog → Deploy

App built, pushed to Artifactory, deployed via Harness CD onto the new compute.

The clean mental model

Terraform builds the house (cluster, network, database). JFrog is the warehouse of versioned, scanned binaries. Harness is the delivery truck — CI stocks the warehouse, CD drives a specific version to the house. Infra changes flow through Terraform; app changes flow through JFrog.