CERTIFICATION is COMPLIANCE made portable. Git is the certification engine. A tag is a badge. A badge is a tag. 255 or reject.
`` cert/{USER}/{TIER}/{YYYY-MM-DD} `
Examples:
Tiers are discovered from DESIGN.md — never hardcoded. Certification levels map 1:1 to MAGIC tiers.
| Tier | Score | Certification Level | Proof |
|---|---|---|---|
| COMMUNITY | 35 | CONTRIBUTOR | CANON.md + VOCAB.md + structure |
| BUSINESS | 43 | DEVELOPER | + {SCOPE}.md spec |
| ENTERPRISE | 63 | CERTIFIED DEVELOPER | + ROADMAP.md + COVERAGE.md |
| AGENT | 127 | SENIOR DEVELOPER | + LEARNING.md (growth evidence) |
| FULL | 255 | PRINCIPAL | + LANG (inherits and extends DESIGN) |
USER scope exists in GOV tree with VITAE.md (identity evidence) magic validate runs on USER scope — returns tier score Score maps to certification level (tier table parsed from DESIGN.md) git tag -s cert/{USER}/{TIER}/{YYYY-MM-DD} — signed, immutable TAGS.md row appended — auditable registry build-surfaces discovers cert tags → compiles _data/developers.json FOUNDATION/DEVELOPERS renders certified developer directory
Anyone can verify a certification:
``bash git checkout cert/{USER}/{TIER}/{DATE} magic validate {USER_SCOPE_PATH}
``
Founder signs (git tag -s) until CI automation is established. Future: Ed25519 via VAULT.
| *CERTIFICATION | COMPLIANCE | MAGIC* |