Skip to content

[P1] Decide verified/ semantics — directory vs badge #352

Description

@Ikalus1988

Problem

The search engine has verified_boost based on ## Verify/Verification sections, but there's also a verified/ directory concept. These are not aligned.

Options

A. Badge only: verified = lesson has ## Verification section. No directory.
B. Directory: verified/ is a physical directory for curated lessons. Search/lessons.json/OKF/MCP all index it.
C. Hybrid: badge determines weight, directory determines inclusion in curated collections.

Acceptance Criteria

  • Decision documented in docs/verified-semantics.md
  • Search engine behavior matches decision
  • lessons.json includes verified lessons
  • MCP server returns verified badge in results

Why

Unifying verified semantics improves search quality and contributor understanding.

Difficulty

🟡 Ring-2 — design decision + implementation.


This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #352 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Ikalus1988 (replace 20 with the amount, and @Ikalus1988 with the user to tip).

📖 If you want to learn more, check out our documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions