Back

Watchlist comparison and observation windows

P14-L04 · P14 · P14-M01

Compare saved observations without inventing continuous monitoring

HISTORICAL · needs_review

Prerequisites: P14-L03

Learning objectives

  • Compare saved observations without inventing continuous monitoring
  • Compute endpoint changes without claiming continuous observation or intervening behavior.

Explanation

An N/N-1 comparison describes two saved observations of the same exact object. It shows endpoint differences. It cannot show every intermediate movement, the cause of a change or uninterrupted provider coverage.

Explanation

Reuse the exact WIF identity from L02. N-1 captured_at is 2026-10-02T06:50:30.221Z, with priceUsd 0.26172428980166795 and marketCapUsd 261493378. N captured_at is 2026-10-02T07:00:29.846Z, with priceUsd 0.2609206096228144 and marketCapUsd 260614125. The pair comes from owner-independent public.zecoin_radar_signal_snapshots; no private Watchlist envelope is involved.

Subtract the UTC capture timestamps: 599625 milliseconds, or 9 minutes 59.625 seconds. Subtract N-1 from N using exact decimal input values: priceUsd delta -0.00080368017885355 and marketCapUsd delta -879253. These are derived endpoint computations, not additional provider observations.

Both endpoints preserve review, riskSignalCount=1, onChainRiskSignalCount=0 and revoked mint/freeze authority states. Their equality is an endpoint comparison, not proof that those states never changed between captures. N has supplied JSON generatedAt and capturedAt; N-1 does not. Leave its JSON timestamps UNKNOWN rather than filling them with database captured_at. Provider coverage, missing intervals and within-window behavior are also UNKNOWN. A sampling window is not a surveillance guarantee.

Historical example

The valid statement is “The saved N value is lower than the saved N-1 value across this window.” The sentence “Price fell continuously for ten minutes while nothing else changed” goes beyond two endpoints and rounds away the actual interval. A price delta does not establish intent, fraud or a financial action.

What the evidence proves

OBSERVED is bounded to the specified saved artifact or explicitly fictional fixture. INFERRED claims name their inputs and assumptions. Two persisted signal endpoints for one exact object; no private Watchlist state or continuous-monitoring proof. N-1 JSON generation/capture times were not supplied.

What the evidence does not prove

UNKNOWN fields remain absent. INSUFFICIENT EVIDENCE does not prove the opposite. No unsupported human attribution, guaranteed safety/profit, financial recommendation or executable transaction follows.

Common mistakes

Promoting UI or aggregate fields into raw provider records; substituting dates across sources; inventing hidden identity or links; treating a timestamp or commercial badge as proof.

Practical exercise

Produce an endpoint table, interval calculation, price/market-cap deltas and an unchanged-field list. Add a gap register. Correct the statement “Watchlist monitored every event, and revoked authorities prove this change is harmless.”

Show worked correction

The table preserves identical chain/mint and both database capture times. Interval=599625 ms. Price delta=-0.00080368017885355; market cap delta=-879253. The five selected integrity/risk/authority fields match at endpoints. Unknowns include intermediate observations, provider coverage/gaps and N-1 JSON times. Repaired statement: “Two saved product observations support endpoint comparisons; continuous coverage, causation and safety are not established.” No private account or live refresh is needed.

Visual specifications

A two-point historical signal timeline with exact endpoint values, dotted unobserved interval and separate rows for unchanged selected flags. Annotate derived deltas differently from saved observations. Never interpolate a smooth path or label the gap continuously monitored.

SPECIFICATION_ONLY — final visual production is not part of this content run.

Checklist

  • Name the exact artifact and identity boundary.
  • Preserve source/time/dataStatus for each claim.
  • Keep OBSERVED, INFERRED, UNKNOWN and INSUFFICIENT EVIDENCE distinct.
  • Preserve limitations without private data or current substitutes.

Summary

  • Artifact integrity is distinct from factual completeness.
  • Origin and timestamp precision survive reuse.
  • A bounded conclusion must survive its unknowns.

Next lesson

P14-L05

Tools

Offline evidence-reading exercise only. No provider refresh, private account access, real-money exercise, wallet signing, entitlement change or runtime output generation.

Sources & claim boundaries

Evidence classifications

HISTORICAL — Two persisted signal endpoints for one exact object; no private Watchlist state or continuous-monitoring proof. N-1 JSON generation/capture times were not supplied.

Observation date

2026-10-02T07:00:29.846Z (specified product/UI time; not universal provider time)

Review status

needs_review

Visual specifications

P14-L04-V01

SPECIFICATION_ONLY · HISTORICAL

Compare saved observations without inventing continuous monitoring

Two persisted signal endpoints for one exact object; no private Watchlist state or continuous-monitoring proof. N-1 JSON generation/capture times were not supplied.

A two-point historical signal timeline with exact endpoint values, dotted unobserved interval and separate rows for unchanged selected flags. Annotate derived deltas differently from saved observations. Never interpolate a smooth path or label the gap continuously monitored.

A two-point historical signal timeline with exact endpoint values, dotted unobserved interval and separate rows for unchanged selected flags. Annotate derived deltas differently from saved observations. Never interpolate a smooth path or label the gap continuously monitored.

Stack each claim/source/time/boundary card at 390 px; keep full IDs readable and wide tables inside local scrollers. Provide the complete text equivalent.

Prose may use RTL; identifiers, exact times and decimal arithmetic remain LTR. Preserve relationship direction.

P14-L04-WIF-N-NMINUS1-20261002-v1

Sources & claim boundaries

PAIR · CONTROLLER_VERIFIED_PRODUCTION_TRANSCRIPTION

Controller-verified owner-independent WIF N/N-1 pair

Supported claim
Specific example and exercise fields/claim boundaries in this lesson
Verification boundary
Two persisted signal endpoints for one exact object; no private Watchlist state or continuous-monitoring proof. N-1 JSON generation/capture times were not supplied.
Checked at
2026-10-02
Open primary source
https://github.com/Samizghal/zecoin/blob/5ad423a67a3c9892fd4e3b6e3464c4f40a7d1795/content/academy-2/datasets/p14-l04/dataset.json

Dataset provenance

id: P14-L04-WIF-N-NMINUS1-20261002-v1

dataStatus: HISTORICAL

observedAt: 2026-10-02T07:00:29.846Z

source: content/academy-2/datasets/p14-l04/dataset.json

scope: Two persisted signal endpoints for one exact object; no private Watchlist state or continuous-monitoring proof. N-1 JSON generation/capture times were not supplied.

Test your reasoning

P14-L04-Q1 · What is the exact elapsed window?
P14-L04-Q2 · What does a negative endpoint price delta establish?
P14-L04-Q3 · May N-1 generatedAt be filled with captured_at?
P14-L04-Q4 · What does equal authority state at both endpoints prove?
P14-L04-Q5 · Which source avoids private Watchlist account access here?