---
name: public-docs-version-not-milestone
description: "Public-facing docs (docs-site) use version numbers, never internal milestone/wave codes"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: c7e38d83-75f7-41a8-9593-2034b5bcc0e0
---

Operator 2026-06-15: public-facing docs (the published `docs-site/src/**` mdBook + llms-full.txt that dev users read) must NEVER carry internal milestone/wave codes (`M12-W3`, `M9`, "wave", etc.). Dev users see **version numbers** instead — e.g. "since v0.7.0", not "(M12-W3)".

**Why:** milestone/wave references are internal project scaffolding, meaningless and confusing to an external adapter/dev user. Versions are the contract surface they actually key on.

**How to apply:** when documenting when a feature landed on a public surface, map the milestone → its shipped version (M12 = v0.7.0). Internal design docs (`CONTEXT.md`, `docs/MANIFEST.md`, ADRs, `*-PLAN.md`, `traceable-reqs.toml`) keep milestone refs — that boundary is fine; the rule is specifically about the published `docs-site` surface. Grep new docs-site edits for `M[0-9]|W[0-9]|wave|milestone` before committing. Relates to [[spt-core-harness-boundary-and-grounding]] (same "don't leak internal/harness specifics onto the public surface" principle).