What does one malformed-website test establish about a guard before HubSpot Company creation? In one candidate and one fixture, the send reached HTTP success and the fixture was correlated with a successful Make execution. The early-filter path itself remains unproven.
The tested condition
The tested guard condition was webhook.website contains scheme marker.
The fixture used the NO_SCHEME_MARKER variant for the website field.
Exactly one send was attempted. Automatic retry was disabled, and delivery recorded HTTP success.
The correlated execution state was EXECUTION_CORRELATED_SUCCESS.
What the execution evidence shows
The frozen technical evidence records a successful Make execution correlated to this fixture.
That is narrower than proving the guard path.
The HubSpot Company creation module is recorded as NOT_CHECKED.
The expected-outcome state is
EXECUTION_MATCHES_DECLARATION_PATH_UNPROVEN.
The available Make execution evidence therefore does not establish whether the Company creation module executed for this run.
Provider observations
No downstream provider artifact was verified absent in this checkpoint.
| Target | Recorded state |
|---|---|
| HubSpot Company | UNKNOWN_API_ERROR |
| HubSpot Contact | UNKNOWN_API_ERROR |
| HubSpot Tasks | UNKNOWN_API_ERROR |
| Gmail welcome message | UNKNOWN_API_ERROR |
| Gmail internal handoff message | UNKNOWN_API_ERROR |
| Calendar kickoff event | UNKNOWN_API_ERROR |
UNKNOWN_API_ERROR is not an absence claim.
These states cannot be used to conclude that a Company, Contact, Task, email, or calendar event was not created.
Human-time evidence
Human-time metrics were not recorded during this experiment.
They were not reconstructed retrospectively from chat timestamps, send timestamps, or other indirect timing data.
For that reason, the canonical failure-mode-result-v1 was not generated.
The retained evidence is a verified technical checkpoint rather than a
canonical failure-mode result.
What this test does not prove
This single fixture does not prove that the malformed-website guard prevented HubSpot Company creation.
It does not prove that the Company creation module was skipped.
It does not prove zero downstream artifacts.
It does not establish universal reliability or behavior outside this one candidate and one fixture.
Evidence used
All article claims come from
benchmark/exp005/evidence/technical-evidence.json.
That evidence is backed by a frozen technical checkpoint and an independent verification receipt. No external source is used to broaden the claims.