TitleChain Foundation · Sophia Registry
M5-CV · Evidence Register

Where the proofs live.

One register. Different evidence states. No assertion laundering.

This register is the index for contributor proof. A LinkedIn profile, company page, certification, GitHub contribution or M5 demonstration can all be evidence — but they do not carry the same weight. The register shows what has been mapped and what still must be bound, demonstrated, contributed or authorized.

DeclaredPublic-source mappedIdentity-boundDemonstratedContributedAuthorizedOutcome verified
Identity rootIAM / TCID
External accountsBound evidence sources
Work proofArtifacts + provenance
Issuer statusFoundation / Sophia
Public defaultPseudonymous capability
01

Contributor proof index

Proof IDCapability domainSource evidenceIAMGitHub / contributionM5 demonstration
FC-0001Founder / Venture ActivationExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0002Business Ops / Community / Digital AssetsExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0003Personal AI / Agent OperationsExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0004Ontology / M5BrainExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0005Revenue / BD / PartnershipsExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0006GTM / AI Commercial TransformationExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0007Project / SOP / OperationsExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0008Talent / RecruitingExisting proof pageStatus on proofStatus on proofStatus on proof
FC-0009Product / Web3 CommercializationPublic sources mappedPendingPendingPending
FC-0010Deep Tech / Semantic SystemsPublic sources mappedPendingPendingPending
FC-0011Regulatory Interop / Cyber ResiliencePublic sources mappedPendingPendingPending
FC-0012Technical Product / AI-Data PlatformsPublic sources mappedPendingPendingPending
FC-0013Enterprise Blockchain / Solutions ArchitecturePublic sources mappedPendingPendingPending
For the early reference cohort, some current pages are design/proof specifications rather than issued production credentials. Production status must come from the verification service, not static HTML.
02

What is stored behind a real proof

Identity evidence

Human root + account bindings

IAM subject, authenticated external-account control, durable account identifiers, consent and disclosure policy.

Capability evidence

Sources + demonstrations

Credentials, work artifacts, assessments, accepted workflows, references and domain-specific demonstrations.

Contribution evidence

GitHub + provenance

Signed commits, pull requests, reviews, documentation, tests, specifications, releases and accepted Foundation artifacts.

03

Proof state ladder

DeclaredMember says it
Source mappedExternal evidence supports it
Identity-boundSource bound to IAM subject
DemonstratedDefined task completed
ContributedArtifact accepted
Authorized / OutcomeQualified scope + real result
04

Open technical role is a proof template too

OR-001

Head of Open Source & GitHub Platform

The role itself is expressed as capabilities and required evidence, so candidates can qualify through proof rather than résumé pattern matching.

Open role proof template →
05

Evidence is not only for people

Human proof

M5-CV / IAM

Skills, demonstrated work, contributions, authorizations and outcomes remain bound to a member-controlled identity root.

Software proof

M5-GitHub

Official source, version/release evidence, contribution provenance and the member's understanding of what she is running.

Open M5-GitHub →
Provider proof

M5-OpenAPI Capability Passport

Provider identity, API capability, permissions, data practices, compatibility, status and revocation are represented separately from marketing claims.

Example provider JSON →
M5 Evidence Register · static demonstration.
Verification model · Contributors