Monitor Observation Gap Ledger

How to use Monitor Observation Gap Ledger

A missing check is not evidence that a page stayed unchanged. Audit the observation schedule and failed attempts before relying on an automation report.

1. Declare the intended UTC polling window, interval and narrow timestamp tolerance.
2. Paste authorized observation records and review missing, failed, duplicate and off-schedule checks separately.
3. Investigate actual monitoring logs and affected pages before making change or outage claims.

Good to know

• At most 500 expected slots; tolerance must be strictly below half the interval. Start plus whole intervals defines expected slots inside the inclusive horizon.
• Missing or failed observations leave change state unknown. Gap windows describe missing expected checks, not known outage durations.
• Each input field is limited to 8,000 UTF-16 characters and each exact-header CSV to 100 data rows. Quoted commas/newlines and doubled quotes are supported. Unsupported controls and unpaired surrogates are refused. Decimal magnitudes are at most 999,999,999 with a smallest nonzero magnitude of 0.000000001; exponents are refused and whole counts are checked exactly. Rational results show at most 18 fractional digits and an ellipsis when more remain.
• Editable Markdown and long-form CSV both retain all summary metrics, context, detailed findings, entered source rows and scope limitations. CSV columns are Record type,Section,Source row,Field,Value; spreadsheet-looking text is apostrophe-prefixed. These are review artifacts, not proof of source truth or a completed real-world task.
• Runs deterministically in this browser. No AI, API, vendor connection, upload, outreach, calendar change, payment, storage or background monitoring. Use authorized pseudonymous records; inspect exports before sharing.