What this attestation records
An onboarding-verification attestation is Extol's on-chain record of what happened during an organization's Pattern 3 setup. It is not a certification that the organization is a valid 501(c)(3), or that the officer's authority to bind the organization has been legally reviewed. It is an abstractor's record: Extol observed these events, from these sources, at these times, and records them faithfully.
The distinction matters. A title abstractor certifies that they searched specific records using a stated methodology; they do not warrant the underlying facts. Extol's onboarding-verification attestation follows the same posture. Anyone consuming the attestation should read it as "Extol observed X" — not "Extol certified Y."
Signer and subject
Signer: Extol KMS credential authority public key.
Subject: the organization's root identity public key.
Payload fields
officer_signup— event details for the officer's Extol account creation (user_id, email, timestamp)org_metadata_entered— the org legal name, EIN, and other fields the officer typed during onboardingteos_lookup— snapshot of the IRS TEOS API response at feature-activation time (status, legal name returned by IRS, deductibility code, response timestamp)feature_activation— the specific feature (e.g., Statement) the officer activated + timestamp + terms_uri acceptedterms_uri— pointer to the versioned Pattern 3 attestation terms in effect at issuance
Notary Spec provenance
source_type:11(system_observed) — Extol observed events during onboardingwitnessing_depth:4(computed_match) — automated observation via Extol's pipelineattestor_relationship:6(institution)confidence:7000— moderate. Extol observed the events faithfully, but the events themselves are self-reports by the officer + an API response. Higher confidence would over-claim the strength of the underlying evidence.
Relationship to signing-time TEOS gate
This attestation records the TEOS status at feature-activation time. It does not substitute for the current-status check performed at every Statement signing attempt. Statement signatures are gated on a fresh TEOS lookup (cached within a 7-day window, refreshed nightly by cron and on-demand at signing time if stale). If an org's TEOS status changes after activation (revocation, status change), the signing gate catches it — this attestation remains historically accurate testimony about state at activation time.