PRINT WATCH

Read-only · private details removed

THE MONITORING CONTRACT

Watch the print. Keep the workshop private.

Print Watch joins a cloud lifecycle signal with a separate camera view, then publishes only the small amount of evidence needed to answer one question: is the print okay?

READ-ONLYNo printer controls 5 SECEvidence cadence 2 SLOTSCurrent + previous
LIVE SIGNAL MAPv1 · PRIVATE-SAFE
01 / SOURCEBambu CloudFixed HTTPS GET
02 / OBSERVELifecycle monitorTwo-sample start gate
03 / PUBLISHprint.arrgee.orgCoarse status + crop

The camera supplies visual evidence through PrintGuard’s loopback path. It does not open a second RTSP connection.

THE PATH FROM PRINT TO PAGE

Four small decisions make the signal useful.

Each stage has a narrow responsibility. A failure becomes visible as a gap, delay, or unavailable state instead of being quietly guessed away.

  1. 01

    Read the cloud state

    A fixed HTTPS GET polls Bambu Cloud every five seconds. Only the observed raw RUNNING value is trusted to start a job.

  2. 02

    Confirm the job

    The monitor requires two fresh, same-job RUNNING samples within fifteen seconds before evidence capture begins. Pause keeps the same job active.

  3. 03

    Capture locally

    Every five seconds, the monitor reads a bounded JPEG from PrintGuard’s loopback current-frame API and records telemetry, score, health, hashes, and any durable gap.

  4. 04

    Publish the smallest useful view

    Sealed evidence becomes a privacy-cropped JPEG and coarse status. The public site retains only current and last; a separate bridge reviews confirmed defects.

TWO PLANES, ONE BOUNDARY

The public page is the quiet end of the system.

Private evidence and public status have different jobs. The boundary is intentional, and it stays visible in every diagram.

PRIVATE / LOCAL

Evidence plane

Job-scoped bundles hold the rolling JPEG ring, redacted observations, score records, health events, gap reports, manifests, and checksums. Sealing is atomic.

owner-only roots · WAL state · bounded ring
PUBLIC / READ-ONLY

Status plane

The site exposes a coarse state, freshness, camera health, progress when available, and two privacy-cropped frame slots. Public requests cannot write.

GET / HEAD · no-store · two slots
SEPARATE / FAILURE-ONLY

Review plane

Telegram is not a lifecycle feed. The bridge accepts only a validated alert event with a matching snapshot, then a human reviews it.

exact alert · matching snapshot · one attempt

EXPLORE THE SYSTEM

Five views, one source-backed picture.

Open a diagram for the shape of the system, then use the evidence index for the exact runtime contract and source links.

A / 01ARCHITECTURE

System architecture

Boundaries, components, transports, storage, status, and the private alert path.

Open viewer B / 02WORKFLOW

Runtime workflow

Start gate, evidence capture, sealing, publication, and confirmed-defect review.

Open viewer C / 03DATA FLOW

Data and evidence flow

Custody and classification from observation to public status and alerts.

Open viewer D / 04LIFECYCLE

Supervisor control rail

Core states, debounce, waiting, sealing, and the fail-closed edges.

Open viewer E / 05SEQUENCE

Poll-to-review sequence

A representative five-second loop, frame read, status ingest, and human review.

Open viewer

Structured specifications are available beside each viewer: architecture.json, workflow.json, dataflow.json, lifecycle.json, and sequence.json.

THE HARD NO

Monitoring does not become control.

There is no pause, stop, cancel, G-code, MQTT, FTP, LAN-only, Developer Mode, or printer-control route in this design. The camera is independent; PrintGuard is camera-only and alert-only.

Return to live status