The page is loading. No inquiry, booking, or provider action is happening in the background.
IronWake uses five proof classes — DEMONSTRATION, INTERNAL_VERIFIED_BUILD, CLIENT_DEPLOYMENT, CLIENT_VERIFIED_RESULT, and QUANTIFIED_VERIFIED_RESULT — and never publishes a claim outside the class it has actually earned.
Audit my workflowVisible to the public
A capability proof exists on ironwake.dev. No client engagement, real customer outcome, or live provider integration is implied. This is the only class that ships without a customer behind it.
Where it appears: Work pages under /work/*, the home hero, and explicit portfolio references.
Visible to the public
The capability is built, deployed, and tested by IronWake against its own acceptance criteria. The evidence is in our build logs, our audit trail, and our internal dashboards — not in a third-party result.
Where it appears: Service pages under /systems/* and capability entries in /services.
Owner only — never copied into public marketing copy
A specific client engagement is live with this capability in production. We can speak to the engagement with the owner present. Names, industries, and outcomes stay gated until the client gives written consent.
Where it appears: Owner-led conversations, post-call summaries, signed SOWs.
Owner only — never copied into public marketing copy
A client has measured an outcome against a defined baseline. The metric, baseline, measurement window, and client signature exist in the engagement record. This evidence is owner-only — it is never copied into public marketing copy.
Where it appears: Internal CRM, owner dashboard, signed measurement report.
Owner only — never copied into public marketing copy
A specific number — bookings recovered, hours saved, response time reduced — has been independently verified by a third party (client finance team, auditor, or signed attestation). The number is owner-only and is never used in marketing copy.
Where it appears: Internal CRM, owner dashboard, signed third-party attestation.
Of the five proof classes, two are owner-only and three are public. The three public labels are the only language IronWake uses on customer-facing pages to describe what is and is not verified.
A capability proof, not a client engagement, result, or provider integration.
A workflow exists, but the external provider connection behind it is not yet verified.
A claim is drafted but has not yet passed the evidence and approval standard this page describes.
A claim is recorded in the truth registry with no evidence. Stays owner-only.
The capability has been implemented inside IronWake and passes its own acceptance tests.
The capability is live for at least one paying client with a signed SOW.
An outcome has been recorded against a defined baseline, signed by the client.
A specific number has been independently verified and signed by a third party.
A claim never graduates to the next proof class because the marketing copy says it did. It graduates when the named evidence — build logs, signed SOW, measurement record, or third-party attestation — exists in the engagement record and is owned by a named person.