aidokitwiki
User Docs Wiki

Badge Vocabulary (canonical)

Closed-set badges for every wiki topic page. First badge is always Audience-…. Second is always Status-…. Remaining 0-2 are Spec-…, ADR-…, or Tier-…. Max 4 badges per page. Every badge MUST link somewhere.

Palette #

Badge Use when Color Links to
Audience-User Top of any user-facing page grey (555555) ../contributing/badge-vocabulary.md
Audience-Contributor Top of any contributor-facing page grey (555555) ../contributing/badge-vocabulary.md
Audience-Adapter%20Author Top of any adapter-author-facing page grey (555555) ../contributing/badge-vocabulary.md
Audience-Stack%20Pack%20Author Top of any stack-pack-author-facing page grey (555555) ../contributing/badge-vocabulary.md
Audience-Maintainer Top of any maintainer-facing page grey (555555) ../contributing/badge-vocabulary.md
Status-Shipped%20v0.5 Page describes shipped behaviour brightgreen ../../.docs/ROADMAP.md
Status-In%20flight%20v1.0 Page describes v1.0-scoped behaviour orange ../../.docs/ROADMAP.md
Status-Post--v1.0 Page is out-of-scope-for-now lightgrey ../../.docs/ROADMAP.md
Spec-Adapter%20Contract Page touches adapter contract blueviolet ../../.docs/docs/specs/adapter-contract.md
Spec-Stack%20Pack Page touches stack-pack contract blueviolet ../../.docs/docs/specs/stack-pack-contract.md
Spec-CLI Page touches CLI surface blueviolet ../../.docs/docs/specs/cli-reference.md
Spec-MCP%20Catalog Page touches MCP catalog blueviolet ../../.docs/docs/specs/mcp-catalog.md
Spec-Conformance Page touches conformance levels blueviolet ../../.docs/docs/specs/conformance-levels.md
Spec-Security Page touches security model blueviolet ../../.docs/docs/specs/security-model.md
ADR-#### Page implements / cites a specific ADR informational ../../.docs/docs/architecture/decisions/####-*.md
Tier-Starter Page is the Starter tier landing blue ../tiers/starter.md
Tier-Standard Page is the Standard tier landing green ../tiers/standard.md
Tier-Strict Page is the Strict tier landing red ../tiers/strict.md

Rules #

  1. Audience is mandatory and first.
  2. Status is mandatory and second.
  3. 0-2 additional badges from Spec / ADR / Tier.
  4. Every badge links somewhere — never decoration-only.
  5. The badge row sits on a single logical line immediately after the H1, before any other content (each badge on its own markdown line is OK; they render inline).
  6. Adjust relative path depth: pages in wiki/<section>/*.md use ../../.docs/…; pages in wiki/index.md use ../.docs/….

Worked example (wiki/concepts/three-layer-architecture.md) #

# Three-Layer Architecture

[![Audience: Contributor](https://img.shields.io/badge/Audience-Contributor-555555.svg)](../../contributing/badge-vocabulary.md)
[![Status: Shipped v0.5](https://img.shields.io/badge/Status-Shipped%20v0.5-brightgreen.svg)](../../../.docs/ROADMAP.md)
[![Spec: Adapter Contract](https://img.shields.io/badge/Spec-Adapter%20Contract-blueviolet.svg)](../../../.docs/docs/specs/adapter-contract.md)
[![ADR-0005](https://img.shields.io/badge/ADR-0005-informational.svg)](../../../.docs/docs/architecture/decisions/0005-adapter-contract-shape.md)

See also #