Advaita Service: echo-frontend

echo-frontend is the user-facing tier (Tier 1) of the echo reference application — a no-build web-component UI served by nginx that submits Nextflow runs and renders the foxfire dashboard. It talks only to echo-backend over /api/*. It runs on Kubernetes (CoreWeave dev/prod, OrbStack local).

What it does

• A launch form: pick N, submit a fibfizz run (POST /api/runs).
• A dashboard: poll run status, task count, and per-task cost (POST /api/graphql), refreshing on a timer and immediately after a launch.

Why it exists

The reference application needs a UI to drive and observe runs. It shows the front-end slot of the pattern: plain custom elements, no build step, served by nginx, talking to a single backend. The same deploy machinery carries it as carries the Wanderland-engine tiers.

How it works

• A static index.html shell loads plain ES-module web components (echo-workflow-submit, echo-run-list) and a small data layer (js/foxfire.js). No build step; the components paint client-side and fetch JSON.
• nginx serves the static assets and proxies /api/* to echo-backend with the prefix stripped: /api/runs → backend /runs, /api/graphql → backend /graphql. /healthz returns 200 from nginx independent of the backend.

Deployment (k8s)

• Image: advaita/echo-frontend (ECR), nginx:1.27-alpine serving the static assets + the web-component JS. Built and pushed by echo-frontend/vivarta.yml.
• Workload: Deployment, container port 8080 (http), probes /healthz.
• Service: ClusterIP on 80 → targetPort http.
• Ingress: nginx, restricted to the VPN source range on dev/prod, TLS via cert-manager (letsencrypt-prod). local is plain HTTP echo.localhost with no whitelist.
• DNS (dev/prod): a CloudFormation Route53 A record (echo-frontend/cfn/dns.yml) → the cluster's nginx-ingress IP; local omits it (per-env !Environment components).
• Namespace: vivarta-echo.

Env	Context	Host
local	orbstack	echo.localhost
dev	useast13-dev	echo-dev.cw.advaitabio.com
prod	useast13-prod	echo.cw.advaitabio.com

Configuration

• nginx.conf: static root + /api/ proxy_pass to echo-backend.vivarta-echo.svc.cluster.local:8080/.
• Deploy pipeline: echo-frontend/vivarta.yml (containerized_deployment; docker_build → ECR; k8s_provisioner + the CFN DNS component on dev/prod; per-env !Environment components + a definitions anchor so local skips DNS). git-sha image tag.

Dependencies

Dependency	Use	Endpoint
echo-backend	launch + reads	echo-backend.vivarta-echo.svc.cluster.local:8080 (via /api/*)
ECR	image registry	advaita/echo-frontend
Route53 (dev/prod)	public DNS	zone cw.advaitabio.com
cert-manager (dev/prod)	TLS	letsencrypt-prod

Dependents

End users via the browser. No in-cluster dependents.

Impact when down

The UI is unreachable; launching and observing runs through the UI stops. The backend, receiver, and any in-flight runs are unaffected. Blast radius is the UI.

The code

• Repo: vivarta-examples (echo-frontend/). Static HTML + web components + nginx. Uncommitted as of 2026-07-01.

Open questions

• Live-cluster verification (ingress, TLS, running image tag): TBD.
• Ingress IP shared with foxfire: TBD verify.
• Dashboard GraphQL field names (runId/status/taskCount/totalCost) vs the deployed foxfire schema: TBD verify against a live foxfire.