Back

Radar source timestamps and limitations

P14-L02 · P14 · P14-M01

Read a saved diagnostic and explain its measurement boundaries

HISTORICAL · needs_review

Prerequisites: P14-L01

Learning objectives

  • Read a saved diagnostic and explain its measurement boundaries
  • Separate product capture time, source time and completeness labels in the saved WIF projection.

Explanation

A saved Radar projection records a product state at a capture time. It does not automatically preserve each provider measurement, source URL or raw response. Read the field and its provenance together. A social timestamp cannot date price, market cap, concentration or authority claims.

Explanation

The accepted object is solana-wif on chain_id=solana, exact mint EKpQGSJtjMFqKZ9KQanSqYXRcF8fBopzLHYxdM65zcjm. Its database locator is public.zecoin_radar_signal_snapshots plus chain, mint and captured_at. The supplied captured_at, snapshot capturedAt and generatedAt all read 2026-10-02T07:00:29.846Z. Their equality is a product-record fact, not three independent provider confirmations.

The projection records dataIntegrityStatus=review, riskSignalCount=1, onChainRiskSignalCount=0, mintAuthorityState=revoked and freezeAuthorityState=revoked. It also records priceUsd=0.2609206096228144, marketCapUsd=260614125, dataQualityCompletenessPct=100, top10AuthoritySharePct=80.0617 and top10TokenAccountSharePct=45.0331. Preserve these as saved product fields, including concentration measure names. Do not conflate token-account concentration with authority concentration or infer beneficial-owner identity.

The social example includes exact-contract mapping attributed to Dexscreener and x_api_v2 with public-post observation time 2026-10-01T00:00:30.547Z. That timestamp remains inside the social boundary. Market/authority provider names, raw payloads and per-field timestamps were not provided. UNKNOWN is therefore the correct entry, even when the product completeness field is 100. This package is an accepted field transcription, not a complete raw diagnostic export.

Historical example

At the saved product capture, both authority fields are revoked and the integrity status is review. The admissible conclusion is that these fields coexist in the accepted projection. It does not establish absolute safety, the absence of other risks, real-time executability or the exact time a provider measured them.

What the evidence proves

OBSERVED is bounded to the specified saved artifact or explicitly fictional fixture. INFERRED claims name their inputs and assumptions. Saved bounded signal fields verified by Controller; executor did not read SQL or obtain full raw provider payloads. Provider timestamps for market/authority fields remain UNKNOWN.

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

Build a provenance register for price, mint authority, top10AuthoritySharePct and the social example. Include exact object, product timestamp, source timestamp, field pointer and limitations. Reject an editor who assigns the social time to every row or rewrites review as safe.

Show worked correction

All four rows retain the exact WIF chain/mint and saved-record locator. Price, authority and concentration point to /record/snapshot and use the product time with provider time UNKNOWN. The social row points to /providerSourceSemantics/boundedSocialExample and carries 2026-10-01T00:00:30.547Z only for that observation. dataQualityCompletenessPct=100 is retained as a stored indicator, not an assurance that missing provenance exists. The conclusion remains bounded product fields; safety and human identity are not established.

Visual specifications

A timestamp/provenance matrix with separate columns for captured_at, generatedAt, field source time and claim boundary. Put the social time only on its own row and shade market/authority source-time cells UNKNOWN. Include both distinct concentration measures.

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-L03

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 — Saved bounded signal fields verified by Controller; executor did not read SQL or obtain full raw provider payloads. Provider timestamps for market/authority fields remain UNKNOWN.

Observation date

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

Review status

needs_review

Visual specifications

P14-L02-V01

SPECIFICATION_ONLY · HISTORICAL

Read a saved diagnostic and explain its measurement boundaries

Saved bounded signal fields verified by Controller; executor did not read SQL or obtain full raw provider payloads. Provider timestamps for market/authority fields remain UNKNOWN.

A timestamp/provenance matrix with separate columns for captured_at, generatedAt, field source time and claim boundary. Put the social time only on its own row and shade market/authority source-time cells UNKNOWN. Include both distinct concentration measures.

A timestamp/provenance matrix with separate columns for captured_at, generatedAt, field source time and claim boundary. Put the social time only on its own row and shade market/authority source-time cells UNKNOWN. Include both distinct concentration measures.

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-L02-WIF-SIGNAL-20261002T070029846Z-v1

Sources & claim boundaries

RADAR · CONTROLLER_VERIFIED_PRODUCTION_TRANSCRIPTION

Controller-verified WIF signal field transcription

Supported claim
Specific example and exercise fields/claim boundaries in this lesson
Verification boundary
Saved bounded signal fields verified by Controller; executor did not read SQL or obtain full raw provider payloads. Provider timestamps for market/authority fields remain UNKNOWN.
Checked at
2026-10-02
Open primary source
https://github.com/Samizghal/zecoin/blob/5ad423a67a3c9892fd4e3b6e3464c4f40a7d1795/content/academy-2/datasets/p14-l02/dataset.json

Dataset provenance

id: P14-L02-WIF-SIGNAL-20261002T070029846Z-v1

dataStatus: HISTORICAL

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

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

scope: Saved bounded signal fields verified by Controller; executor did not read SQL or obtain full raw provider payloads. Provider timestamps for market/authority fields remain UNKNOWN.

Test your reasoning

P14-L02-Q1 · Which time can be assigned to price as its independent provider measurement time?
P14-L02-Q2 · What does completeness 100 establish?
P14-L02-Q3 · Can revoked mint/freeze fields coexist with integrity review?
P14-L02-Q4 · Why retain exact chain and mint with the locator?
P14-L02-Q5 · Are top10AuthoritySharePct and top10TokenAccountSharePct interchangeable?