Technical Standards Revision Monitor

Monitor a deliberately narrow set of official IETF and W3C standards for status, supersession, metadata, section, reference, and RFC 2119/8174 normative-language changes with exact evidence.

What this does not do

• No unauthorized retrieval of paywalled ISO, IEC, ASTM, IEEE, or other licensed full text.
• No legal or compliance certification.
• No universal standards database.
• No interpretation of whether a system complies.
• No LLM summary.
• No cross-site crawling.

Sources and authorization

Version 1 reads only public official RFC Editor pages, IETF Datatracker/Internet-Draft records, and W3C Technical Reports. Other providers and non-official URLs are rejected before any request. Source terms remain controlling; see SOURCE_POLICY.md and source_contracts/.

Input

Provide 1-100 standards using provider (ietf or w3c) and exactly one identifier or official url. Optional baselineStoreId enables persistent comparisons. sections limits full-text checks to exact official section identifiers/titles. includeNormativeDiff defaults to true, retainRaw to false, and concurrency is 1-6.

{"standards":[{"provider":"ietf","identifier":"RFC9110"}],"includeNormativeDiff":true,"concurrency":1}

Output

Each result row contains the standard's exact official status and relations, canonical baseline hash, stable change classes, before/after section excerpts, source hashes and attribution, warnings, billing decision, and KVS artifact manifests. Example:

{"recordType":"result","status":"baseline_created","charge":{"event":"standard-check","chargeable":true},"standard":{"provider":"ietf","identifier":"RFC9110"},"changes":[],"baseline":{"mode":"stateless","changed":false,"committed":false}}

One final run-summary row is pushed without a billing event. Large deterministic diffs and optional raw source bytes use generated safe KVS keys; each manifest records content type, byte length, SHA-256, schema version, and generation rule.

Pricing

The primary PPE event is exactly standard-check at launch price $0.05 per accepted standard check. Maximum event cost is number of standards × $0.05; 20 standards cost at most $1.00. Baseline creation, unchanged, changed, superseded/obsolete, expired, and definitive not-found checks charge. Invalid input, provider outage, blocked source, parse failure, and exhausted rate limits do not.

State and baseline behavior

Without baselineStoreId, every valid check is stateless baseline creation. With it, canonical parsed documents are journaled before billing but become current only after Apify reports exactly one accepted event. Charged-but-uncommitted journals are recovered on the next run. Observation timestamps, run IDs, retries, and platform metadata never enter canonical hashes.

Partial failures and negative results

Each standard is isolated. A 404/410 definitive official not-found is a paid terminal result. 429, provider 5xx/outage, malformed content, missing requested sections, and blocked sources are uncharged. Full-text-dependent failures never advance a baseline. Once Apify reports the event charge cap reached, no later batch is scheduled.

Resources

Minimum 256 MB, default 1024 MB, maximum 2048 MB, hosted timeout 600 seconds, concurrency at most 6, and each source response capped at 4 MB.

Data handling, privacy, and deletion

Inputs contain no credential field. Output echoes only validated public locators. Raw text is not retained unless requested. Delete the run dataset and selected KVS/baseline store to remove retained data; see PRIVACY.md.

Source rights and attribution

IETF/RFC Editor and W3C attribution and source evidence accompany every successful row. This Actor does not redistribute licensed standards and does not override upstream notices.

Limitations

HTML structure and official metadata can change. Normative keywords are reported as textual evidence only; count changes are never labeled as compliance findings. Internet-Draft expiration, withdrawal, and replacement remain distinct official statuses.

Support and changelog

See SUPPORT.md for reproducible reports and CHANGELOG.md for version history.