screenrigstatus

MARKETING + DOCS HTTPS VERIFIED · NOT UPTIME. Service API, Player, release hosts, protected content, and the full production application stack remain undeployed and unverified.

path: /status/ · observed 2026-08-14view as markdown →

status · checkpoint 02

The complete localhost v1 signal path is verified.

ScreenRig is an agent-operated digital-signage service: an agent uses the CLI and REST API to upload content, assemble a looping playlist, pair a browser screen, and observe the result.

The public marketing and documentation site is live and verified over HTTPS. Service readiness remains source and black-box localhost acceptance evidence, not an availability, latency, SLA, customer, traffic, or production-health report.

Acceptance record

Black-box E2E
118 pass · 0 fail · 0 blocked · 10 deferred
Persistent matrix
41 pass · 10 deferred
Health / readiness
/.health and /.ready returned HTTP 200 with no degraded dependencies; nine local services were left running for the owning integration task.
Contract
OpenAPI 0.2.0 with 19 acceptance assertions verified.

Component readiness

Marketing + docspublic HTTPS verified
CLIfull local lifecycle npm unpublished
SDKlive bridge verified npm unpublished
Playerdesktop + mobile E2E
Android containersource matrices pass hardware unvalidated
Backendthree replicas verified
Pairingsix-character lifecycle
OpenAPIv0.2.0 verified
npm packagesnot published
Service productionnot deployed API, Player, release hosts, protected content, and full stack unverified

read status.json

Deferred or not production-proven

  • MCP, billing/payments, screenshots, email recovery, and a management dashboard remain outside v1.
  • Android standard/managed/Amazon source and its native content contract are implemented; instrumentation is blocked without KVM, no personal Pixel, managed physical device, or Amazon Signage Stick was validated, no app is store-published, and there is no general offline guarantee.
  • The marketing and documentation site is publicly live over HTTPS. The service API, Player, release hosts, protected content delivery, first signed application release, and full production application stack remain undeployed or unverified.
  • The local extractor proof runs under the local development boundary; actual production rootless child isolation still needs first-release proof.