Skip to content

docs: establish permissioned adoption evidence process - #205

Merged
codeforester merged 1 commit into
mainfrom
enhancement/196-20260809-adoption-evidence
Aug 9, 2026
Merged

docs: establish permissioned adoption evidence process#205
codeforester merged 1 commit into
mainfrom
enhancement/196-20260809-adoption-evidence

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Closes #196

Summary

  • document the permissioned adopter program and distinguish customer evidence from maintained fixtures
  • record the honest current status: zero confirmed independent adopters, target three
  • emit dated, revision-bound compatibility evidence artifacts from the reference-consumer workflow
  • correct compatibility wording so Base and adjacent repositories are not counted as external adoption

Validation

  • python scripts/record_compatibility_evidence.py
  • python scripts/validate_consumers.py
  • python scripts/validate_docs.py
  • ./tests/validate.sh
  • python -m mkdocs build --strict
  • ruff check and format

@codeforester
codeforester force-pushed the enhancement/196-20260809-adoption-evidence branch from 975527a to 45a6001 Compare August 9, 2026 17:08
@codeforester
codeforester force-pushed the enhancement/196-20260809-adoption-evidence branch from 45a6001 to b9bf82c Compare August 9, 2026 17:10
@codeforester
codeforester merged commit 211afae into main Aug 9, 2026
88 of 90 checks passed
@codeforester
codeforester deleted the enhancement/196-20260809-adoption-evidence branch August 9, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v1.0] Establish independent adoption and compatibility evidence

1 participant