CONTINUOUS MONITORING

Every release, witnessed.

A standing check on a model — or a whole family. Every new finetune or release that lands is detected to a pinned schema, witnessed, and diffed against the version before it — so a team’s trust in what it ships never goes stale.

STAGED · THE RECURRING WATCH
STAGED · THE RECURRING WATCH

Every release witnessed and diffed against the one before it — a live, honest account that never goes stale.

STAGED

The same read, run forever.

Where a one-time audit is a single deep read, monitoring is that same DETECT run incrementally, on models that keep changing. Each new version is checked, witnessed, and set against the one before it — a live, honest account of what each release actually did, and whether it hid anything.

It runs on a single model, or across a whole family — the fleet view that feeds portfolio analytics. Every checkpoint emits a signed attestation the team keeps as evidence, kept in the open on the record. It is assurance against drift, misconfiguration, and accidental or planted misalignment — evidence, not certification.

DETECT · ATTEST

Open models move constantly — a base gets finetuned, a finetune re-finetuned, a provider ships v2. Monitoring answers, continuously and with witnesses, what did this release actually do, and did it hide anything?

What it does, every release.

Each version that lands runs the same steps, in the same order — pinned, so releases stay comparable and the account never drifts under you.

  • Detect to the pinned schema. The same finding taxonomy every time, so one release can be read straight against the last.
  • Witness every finding. Replayable, the same as every other surface — a claim you can re-run, not a verdict you have to take on faith.
  • Diff against the last release. What changed, and whether anything undisclosed appeared — each change witnessed — plus a drift signal: how far this release moved, and toward what. For the mid-run alarm, see drift guard.
  • Abstain honestly. Whatever the new release makes newly un-provable is surfaced plainly, not smoothed over.
  • Alert and attest. A material or hidden change is routed to the team; each checkpoint emits a signed, keepable attestation. When a change needs removing, excise is the on-ramp.

Incremental by construction.

Reading every release from scratch would be unaffordable at cadence. So only the change is read deeply — and the same release always reads the same.

Only the change is read

Only what a release actually changed is re-detected in depth. Unchanged, content-addressed behavior is served from cache — so the watch stays affordable at release cadence.

The trail does not flap

Fingerprints are stable and deterministic, so re-running the same release is idempotent — the same finding yields the same witness, checkpoint after checkpoint.

Two results the watch stands on.

The full battery lives on the record. Two that carry the recurring watch — the diff that surfaces a hidden change, and the fingerprint that keeps the trail steady. Pick one to read it.

REL·Δ

An undisclosed behavior, caught in the diff

● WITNESSED DETECTION

Read against a real-world baseline alone, a release sits at chance — Protora says so rather than guess. Set against a reference — for monitoring, the version before it — an undisclosed change surfaces as a witnessed detection.

chanceMODEL vs REAL, ALONE
1.5–3%OF THE CHANGE, SURFACED AS SIGNAL — REFERENCE-DIFFERENTIAL

A detection signal, not localization: it witnesses that something changed, not where. Without a reference, it abstains.

REFERENCE = PRIOR RELEASE · DETECTION SIGNAL, NOT LOCALIZATION · LOCALIZATION CLAIM TESTED CONFOUNDED, DOES NOT SHIP · ABSTAINS WITHOUT A REFERENCE
WHAT THE WATCH WILL NOT DO

A change is surfaced, not smoothed. The watch never quietly reconciles two versions to look stable — if a release moved, you see it move.

Hidden change is first-class. An undisclosed behavior appearing is exactly what a team needs to know — so the diff treats it as a finding, not noise.

Bounded, and witnessed. The trail reports what changed and that it holds — findings and attestation — at or below the published ceiling.

Put a standing watch on the
models you keep shipping.

Monitoring is staged — the recurring engine built on the audit that’s open today. Start with one deep read; the standing watch wires in as it lands, and every checkpoint stays yours as evidence.

Every engagement is scoped per case and quoted per offer — tell us what you need, and we’ll scope it and send you an offer.