Run locally

Local validation status: the pinned Linux/amd64 gateway image passed HTTP safety checks and all three Explain interactions in a browser. The three-service Compose integration and browser journey also passed with loopback-only port bindings and a clearly labeled local healthcheck override. Under x86 emulation on an ARM host, the source’s two-second Python healthcheck timeout expired despite healthy HTTP responses; the local rehearsal used 15 seconds. The original timing budget is not validated by that qualified pass. No current hosted deployment is attested here.

Get the exact source

Use Python 3.11–3.13, Git, and Docker with Compose support. The application dependency specifications contain version ranges; the source pin alone does not freeze every Python dependency.

git clone https://github.com/Seemorghdev/edge-evidence-reference-platform-public.git
cd edge-evidence-reference-platform-public
git checkout --detach 37e8a8f9a34ff04eea621d146fea078632ed9125
python3 -m venv .venv
. .venv/bin/activate
python scripts/install_workspace.py --dev
make check

make check includes lint, tests, the projection guard and Compose configuration validation. It requires a functioning Docker/Compose installation. No provider credential or cloud account is needed for the documented local path.

Option A: three services with Compose

docker compose -f deploy/compose/docker-compose.yml \
  up --build evidence-api edge-agent web-ui

Open http://localhost:8082/. Expect three examples: complete, deferred and prepared. Explain should produce a non-empty response for each.

curl -fsS http://localhost:8080/healthz
curl -fsS http://localhost:8080/api/v1/artifacts
curl -fsS http://localhost:8081/health
docker compose -f deploy/compose/docker-compose.yml \
  --profile tools run --rm integration-runner

The Agent health response includes mutation_authorized: false. The integration runner retrieves the projections and requests inspection; it does not execute workers.

Stop the foreground command with Ctrl+C, then clean up the local services:

docker compose -f deploy/compose/docker-compose.yml down --remove-orphans

Option B: the same-origin gateway container

The pinned container workflow builds Linux amd64 and tests a non-default assigned port. Run these commands from the source checkout; choose unused loopback ports.

docker build --platform linux/amd64 --provenance=false --sbom=false \
  -f services/web-ui/Dockerfile.gateway -t edge-evidence-gateway:review .
docker run -d --name edge-evidence-gateway-review \
  -e PORT=18083 -p 127.0.0.1:18083:18083 edge-evidence-gateway:review

Once startup completes, open http://127.0.0.1:18083/ and check:

curl -fsS http://127.0.0.1:18083/healthz
curl -fsS http://127.0.0.1:18083/readyz
curl -fsS http://127.0.0.1:18083/api/v1/artifacts

Expect health ok, readiness ready with authority: synthetic-only, and three artifacts. Use Explain on all three cards. Verify that each response matches the selected artifact and reports no mutation authority.

The reset route is deliberately absent:

curl -s -o /dev/null -w '%{http_code}\n' -X POST \
  http://127.0.0.1:18083/api/v1/demo/reset
# Expected: 404

Clean up only the container created above:

docker stop edge-evidence-gateway-review
docker rm edge-evidence-gateway-review

What this validates

Successful local execution would establish the tested behavior for that environment and candidate—not production readiness, engineering acceptance or a live hosted deployment. See boundaries and verification.

The healthz and readyz examples here are local checks. They are not instructions for probing a Google Cloud deployment.