Creator adoption

Identity first

Launching around someone is not proof of endorsement. At /verify, sign in, connect GitHub and verify a Solana wallet through Clerk. Evangel checks GitHub directly: personal repository ownership, admin or maintainer permissions, or an authored merged pull request for contributor history. Organization membership and write access alone do not establish ownership. Public non-fork GitHub repositories are currently supported.

The factory authority approves the exact owner and terms hash. There is a two-day challenge window. Finalization releases 1% upfront for coin projects; tokenless funding repositories receive no automatic SOL payout.

Disputed identity

A challenge pauses adoption. The agent must review again; invalid candidates can be rejected by the authority. Source identity remains an evidence-review responsibility, not a claim inferred from an account name.

Fresh checks before approval

The governor requires an identity.userId in adoption and worker-award requests and independently rechecks GitHub and the verified wallet during both evaluation and verification. Adoption requires owner, admin or maintainer authority for the project source; contributor history alone cannot claim a project. Workers may be new contributors: verified identity does not replace delivery evidence or milestone acceptance.

The verification response is a short-lived informational result, not a signed payment authorization. Never trust a copied badge or client-supplied role. Stable GitHub user and repository IDs are included in review context. Squads reviewers still approve the exact transaction; these offchain checks do not add an onchain OAuth oracle or remove the quorum requirement.

GitHub OAuth and Solana wallet connections must be enabled in Clerk. Public production authentication requires a configured live instance and evangel.fund domain. No private keys, OAuth access tokens or wallet signatures are exposed by the verification API.