From application to revocation. Every step has an owner.

A structured intake. Firm metadata, capability declaration, three live references, two redacted case studies, and a security-baseline self-assessment.

Roughly 35% of applications advance to full audit. Most declines are at the references and security artifacts, not technical depth.

Five pillars scored independently on the L0–L4 scale published in the rubric. Two reviewers per pillar, disagreements escalated to a calibration call. Evidence is captured in the audit packet and retained for the membership term.

Borderline files receive a recorded calibration discussion. The audit packet is what would be shown to a buyer's counsel under NDA. It is built for that audience.

On a pass decision, a verification record is created with a permanent badge ID, the rubric version cleared, tier, and vetting date. The embed snippet and live verification URL are issued through the agency portal.

Pre-issuance use of the mark. Including in proposals or live RFPs. Is grounds for permanent disqualification. The badge is live-rendered; static copies will not verify.

Profile is built from the audit packet, agency-supplied case studies, and the capability declaration. Placement weight is a function of tier, recency, and intro outcomes. Not pay-to-play.

Featured placement is included at Backed; co-marketed top placement at Managed. Verified holders are listed; placement weight is earned, not purchased.

The named US liaison is assigned, introduced to the agency principal, and walked through the live engagement portfolio. Escalation paths, comms templates, and the covered-call calendar are configured.

The liaison is not your project manager. Coverage is bounded to pitch, kickoff, escalation, and milestone-gate calls. Standups and routine status are explicitly excluded by contract.

Every introduction is stamped with an attribution code (prevouched_sourced, liaison_assisted, agency_sourced) at origination. Codes are reconciled monthly against agency-reported pipeline.

Attribution is encoded, not negotiated after the fact. Disputes are reviewed by a partner who did not work the deal; published reversal rate appears in the changelog.

Liaison sends expectation-setting comms at kickoff, attends covered calls, handles escalation in writing, and gates milestones. Async load is poolable, which is what makes the model scale.

Most engagements never reach escalation. The expectation-setting memo is the single most predictive artifact for whether they will.

QA flags accumulate from client complaints, missed SLAs, and security events. Severe events trigger immediate review; the verification page and directory update within 15 minutes of a revocation decision.

A mark that cannot be lost is not trust. Published revocations are recorded in the changelog without retraction.