Level credentials

Draft specification recording Bob's chosen names. This does not open a level, award a credential, change the signed objectives, or implement issuance. Bob approves the design before use.

Names

Topic names below come unchanged from each level's objectives.yml.

LevelExisting topic nameCredential name (Bob's decision)
100How AI works: AI at work and in lifeOpen Certificate in AI Literacy
200Using gen AI wellOpen Certificate in Applied AI Practice
300Building with gen AIOpen Certificate in Building with AI
400Engineering AI systemsAiGovOps Foundation Open Mastery in AI Engineering and Assurance (free)
500Governance, safety and researchAiGovOps Foundation Open Advanced Mastery in AI Governance, Safety and Research (free)

Every certificate carries this exact line:

Free and open. Every source cited. Human-reviewed.

Naming rule: use “Mastery” and “Certificate” only. Never name or market these credentials as “degree”, “Master of”, “MS”, “accredited” or “university”. Unaccredited “master's” wording is restricted in several US states; this is a conservative naming constraint, not a claim of accreditation or a state-by-state legal assessment. None of these credentials implies a vendor certification.

Learner process

The content-side gates in TRUTH-STANDARD.md are preconditions for a level being open to learners, not steps the learner must perform. Reviewers are people: one subject expert and one audience reader per module. A separate checker checks the sources; the writer never checks their own work. Red-team findings go to the human red-team lead; accepted findings must be resolved. The board signs the level after its modules pass review. Bob and Ken retain the publish gate.

flowchart TD
    S["Every module: separate source check"] --> R["Red-team check; accepted findings resolved"]
    R --> H["Two human reviewers per module"]
    H --> B["Level board sign-off"]
    B --> O["Level open to learners after Bob and Ken's publish yes"]
    P["Placement test: entry at 100, 200 or 300"] --> M["Level modules: plain / standard / technical; same objectives"]
    O --> M
    M --> Q["Each module: 5-question quiz and workbook"]
    Q --> J["Level project reviewed by a person; at 100, a host on Ken's Thursday call"]
    J --> A{"Project approved?"}
    A -->|"Not yet: revise"| J
    A -->|Yes| C["Credential issued: Beacon signed receipt"]
    C --> N["Next level; after 500, ladder complete"]
    N -->|"Next level must also be open"| M
    M -. "From 300 up: optional cert-prep rails" .-> V["Prepare for vendor-proctored exams; learner sits vendor exam separately"]
  1. Take the placement test. It routes entry to 100, 200 or 300, not directly to 400 or 500.
  2. Work through an open level's modules in plain, standard or technical gear. All gears teach the same objectives and share the same quiz.
  3. Complete each module's five-question quiz and workbook exercise.
  4. Complete the level project and have a person review it. At 100, a host on Ken's Thursday call marks the project. Revise if it is not approved; payment cannot replace approval.
  5. After approval, receive the level credential as a signed receipt. Earned, never bought.
  6. Move to the next open level. Level 500 follows completion of 400. From 300 up, optional prep rails lead toward vendor-proctored exams, as CURRICULUM.md describes. We prepare learners; we never sit the exams. Bob must clear each vendor name.

Certificate design and record

The landscape mockup uses Ada Example at Level 400. It is visibly marked SAMPLE and is not a credential. Cream, green, charcoal and gold follow the Wren Café palette in apps/viewer/src/style.css. The self-contained SVG uses the site's serif/sans/mono font stacks with local fallbacks; it fetches no fonts or other assets. Typed signatory names are not signature images. The certificate is in English. Its decorative hex band encodes the receipt ID as uppercase, space-separated hexadecimal bytes of the ID's UTF-8 text. Decoding the band gives the same ID printed in plain text. It adds no security and is not a signature. Verifiers use the verification URL to check the signed receipt and its current status.

FieldDesign and record requirement
Learner nameAs the learner chooses; no legal-name requirement
Credential nameExact name from the table, including “(free)” at 400 and 500
Level100, 200, 300, 400 or 500
Issue dateDate of issuance; placeholder only in the sample
Project titleLearner-approved, public-safe title only; no project text
Reviewing hostPerson who approved the project; not an agent
Receipt IDUnique identifier for the signed record
Verification URL / QRCompressed record in the URL fragment; https://verify.aigovops.org/ from its own Pages repository (Bob, 20 Nov 2026); the TEST preview stays on GitHub Pages until then
SignatoriesBob Rapp and Ken Johnston, each “Founder and Co-chair, Review Board”. Titles set by Bob Rapp on 20 Nov 2026; Ken Johnston agreed (relayed by Bob, 20 Nov 2026).
Required lines“Free and open. Every source cited. Human-reviewed.” and “Earned, never bought.”

Beacon, the existing credential agent, signs the credential record with Ed25519 after the human project approval. The visual certificate refers to that receipt; typed names or signature images do not replace the cryptographic signature. This specification does not add a second issuer or implement a signing service.

The verification record contains only the certificate fields and the evidence needed to verify its signature and current status. No private content: no quiz answers, no project text, no email. Learners must choose public-safe names and titles before issuance; private review material stays outside the credential record. The mockup's host, date, receipt and URL are explicit placeholders.

Revocation and errata

A credential can be revoked or reissued. Verification shows its current status (valid, revoked or superseded), not merely that an old signature was once valid. Corrections produce a replacement receipt linked to the earlier receipt; the earlier record shows that it was superseded. Do not silently alter a signed record. Keep any public revocation reason free of private learner content.

See CREDENTIALS-PLAN.md for the proposed issuance plan.

Open items — human decisions needed

Until the outstanding items are settled, the mockup remains a sample, not an approved issuance template.