Skip to content

ScreamingFace evidence and status

The revision table below is a dated 2026-07-31 acceptance receipt. It is not current deployment status. Dev pins now advance automatically under ADR-0008. Verify current source revisions and running digests from Git, Argo, and the cluster before making a current-state claim. The staging and production program owns future environment gates.

This page separates deployment provenance, reconciliation, continuous liveness/security checks, milestone functional acceptance, and known limitations. They answer different questions and must not be collapsed into a single "green" status.

Field Last verified value
Environment Dev on aks-dev
Public hostname fusion.dev.screamingface.ai
Tenant revision a6f67356b98d407965be2a9e0a763ac07f503959
Infrastructure/Argo revision 0a8e760af4a37a3fc3d5c4ecb85f1f304f80e787
Cluster and continuous-check verification 2026-07-31T06:42:12Z
Full public functional verification 2026-07-31, including a successful run after trial retirement

Claim and evidence matrix

Claim Evidence Frequency Last verified Result and boundary
Exact tenant charts fetched Argo source revisions on screamingface-url4-cloud and screamingface-sf-aigw Every reconcile 2026-07-31T06:42:12Z Both include tenant revision a6f67356… and infrastructure revision 0a8e760…
Exact images running Kubelet imageID on each stable Deployment Every pin and cutover 2026-07-31T06:42:12Z Both full digests match the immutable rollout inputs
Workloads reconciled Argo sync and health Every reconcile 2026-07-31T06:42:12Z All six ScreamingFace Applications were Synced/Healthy; this is not functional proof
Migration succeeded Argo operation record for aigw-migrate Every aigateway upgrade 2026-07-31T02:07:50Z Hook phase Succeeded
Public edge rejects unauthenticated traffic Gatus Fusion edge enforcement 60 seconds 2026-07-31T06:41:50Z 302/403 proves Cloudflare Access enforcement only
url4-cloud answers its health endpoint Gatus url4-cloud health 60 seconds 2026-07-31T06:41:52Z HTTP 200 proves process, Service, and NetworkPolicy reachability
aigateway answers its health endpoint Gatus AI gateway health 60 seconds 2026-07-31T06:42:12Z HTTP 200 proves process, Service, and NetworkPolicy reachability
Platform and boundary behavior Gateway and workload boundary acceptance suite Release and cutover 2026-07-31 10/10, including allowed and denied paths
Runner and JetStream lifecycle Public local-expression acceptance Release and cutover 2026-07-31 Complete six-event lifecycle in 3.0 seconds before retirement and complete lifecycle again after retirement
WebSocket timeout behavior Attached public socket plus post-hold control Release and cutover 2026-07-31 ~06:30Z Socket remained open for 110 seconds with seven heartbeats; the next fresh run completed
Service identity shape Authenticated /whoami through the public edge Identity or edge changes 2026-07-31 ~06:30Z Verified service identity mapped to x-service-id; x-tenant identified sf-fusion; no x-user-email was present
Provider completion Provider-backed functional canary Release and cutover 2026-07-31 Not proven; model and profile contracts remain open

Immutable deployment proof

Workload Tenant source Requested tag Running image digest
url4-cloud a6f67356b98d407965be2a9e0a763ac07f503959 main-a6f6735 sha256:19e87a5a008c671e321c9ad1b17c5479dde2d8fb34b51633ec40fd56875a581e
aigateway a6f67356b98d407965be2a9e0a763ac07f503959 main-a6f6735 sha256:c78f924955e563c9acdb0a5dbff537670c779202adbb7e7f2e33fd1fc92a38ca

Tags are convenient deployment inputs; the running kubelet digest is the immutable artifact proof. Argo health alone cannot establish that the expected image content is running.

Trial retirement proof

Infrastructure PR #175 retired the trial on 2026-07-31. A live inventory after Argo pruning showed only the intended sf-fusion survivors:

  • Deployments: url4-cloud, whoami;
  • Services: nats, nats-headless, url4-cloud, whoami;
  • persistent storage: only the NATS JetStream PVC;
  • ExternalSecrets: url4-cloud-auth, demo-upstream-cred;
  • eight current NetworkPolicies.

The trial url4, aigateway, database Deployment/PVC, old ExternalSecrets, and obsolete policies no longer exist. The deleted trial database data is not a rollback source. A full public six-event lifecycle and all three continuous checks passed after pruning.

Continuous checks

The Tenant · sf-fusion status group runs three checks every 60 seconds:

Check Path Success condition It does not prove
Fusion edge enforcement Public /whoami, without credentials Cloudflare returns 302 or 403 Authenticated application behavior
url4-cloud health In-cluster /healthz on port 9108 HTTP 200 NATS, Runner Jobs, WebSocket attach, or aigateway
AI gateway health In-cluster /healthz on port 9105 HTTP 200 Provider credentials, profiles, spend controls, or model completion

When the checks first reconciled, the AI gateway probe timed out twice while the new status path settled, then passed on successive intervals. The values above are the last directly observed successful executions, not a claim of uninterrupted historical uptime.

Last full functional acceptance

The accepted public path was:

  1. mint a short-lived capability through POST /token;
  2. open the ticketed public WebSocket;
  3. send ai.url4.attach with from_sequence: 1;
  4. submit the local expression through the REST surface;
  5. receive HTTP 202;
  6. observe started, two span events, cost.usage, result, and terminated over the attached socket.

The lifecycle completed in 3.0 seconds. The attached socket then remained open for 110 seconds with seven heartbeats—longer than the route's 90-second REST timeout—and was never closed by that timeout. A fresh token, socket, and expression completed after the hold.

After the trial resources were pruned, a new public request again returned HTTP 202 and delivered started, two span events, cost.usage, result, and terminated. This proves the surviving tenant-owned path remained functional without the trial objects.

This proves the public edge, capability flow, explicit attach, Runner, JetStream lifecycle, and unlimited /ws timeout together. The local expression does not invoke a model provider, so it cannot prove provider completion.

No capability, Cloudflare credential, service identifier, provider credential, prompt body, or result body is retained in this documentation.

How to read the current status

  • Argo Synced/Healthy means the desired resources reconciled and Kubernetes health assessment passed.
  • Gatus green means only the named endpoint returned the expected status during its latest interval.
  • Functional acceptance passed means the multi-component protocol path worked at the recorded revisions and timestamp.
  • Provider completion not proven means a real model response with an approved profile and spend control is still an open acceptance gate.

Known limitations

  1. The default Anthropic model identifier is not provider-prefixed as required by aigateway.
  2. WebSocket connection can be counted before protocol attach succeeds.
  3. Header-derived identities do not yet have an approved provider-profile and spend-cap provisioning contract.
  4. Capability tickets have a 60-second lifetime; new runs need fresh tickets.
  5. Cloudflare bot protection requires programmatic clients to set a real User-Agent.
  6. Production is dark: no anonymous route exists there, and the first promoter-pressed production promotion has not happened yet (every production pin so far landed as a PR at staging's pin).

Maintenance

Update this page in the same change that alters a chart revision, image pin, health path, Gatus check, route, identity contract, functional result, or known limitation. Historical evidence should retain its timestamp; current-state rows must be re-verified rather than silently carrying an old result forward.

Return to the ScreamingFace quick rundown.