Archived command-line experiment

You approved it.
Did it stay
that way?

A small Python utility compared saved HTML with an explicitly approved contact-path contract. The source is preserved as an engineering experiment.

Local CLI · no live scans, schedule or hosted monitoring.

Fictional studio · /contactChange detected
Illustrative check · synthetic data
The contact button points somewhere new.
ButtonStart a project
Approvedhttps://studio.example/contact
Observedhttps://studio.example/old-contact
Next stepConfirm the change with the site owner and restore the intended link if needed.

This sample shows a changed link. It does not establish that a lead was lost or that a form delivers email.

A small, explicit contract

Check what matters
on the pages you choose.

Start with the expected contact path. Compare the page against it. Keep intentional changes separate from changes that need attention.

01

Agree on the baseline

Name the important button, its destination, the form fields and the contact details that should be present.

02

Find specific differences

Identify missing elements or changed values in the page HTML, with expected and observed evidence.

03

Make investigation easier

Get a focused report and a suggested next step. Review changes before approving a new baseline.

ARCHIVED · LOCAL CLI

Small checks.
Clear evidence.

Launchguard reads saved HTML and compares it with a reviewed contract for one contact path. It does not crawl, fetch pages automatically, send alerts, or keep a monitoring history.

What the source checks
Approved link destinations, form actions and field names, and specified visible contact text.
What it cannot establish
JavaScript-rendered behavior, form delivery, mailbox receipt, uptime or customer outcomes.
How to try it
Run the Python command-line tool locally with the included fictional contract and HTML examples.