Skip to content

v9.2 - rules-first governance and portable support artifacts

Choose a tag to compare

View all tags
@DarKWinGTM DarKWinGTM released this 08 Apr 20:02
· 220 commits to master since this release
v9.2
a8894f7

Summary

This release tightens two governance areas in the RULES repository:

  • direct human-readable wording over metaphor-heavy internal shorthand
  • rules-first handling for user-declared governance issues, plus portable-by-default support/package source artifacts

Included rule updates

  • accurate-communication -> v2.12
  • explanation-quality -> v2.9
  • natural-professional-communication -> v1.1
  • answer-presentation -> v1.14
  • authority-and-scope -> v2.0
  • portable-implementation-and-hardcoding-control -> v1.2
  • project-documentation-standards -> v2.15
  • document-consistency -> v1.6
  • master design / README / TODO / phase / changelog synchronized to v9.2

Behavioral changes

Direct human-readable wording

The communication-owner set now prefers direct action/result wording over metaphor-heavy internal shorthand when a plain statement would make the practical meaning clearer immediately.

RULES-first over memory-first

When the user explicitly says an issue should be solved in RULES rather than memory, the assistant must keep the fix on the RULES path instead of treating a memory write as the substitute remedy for that same issue.

Portable support/package source artifacts

Reusable support/package source artifacts such as plugin-owned docs, scripts, skills, and agents are now explicitly portable-by-default and should not bake workstation-specific absolute paths into reusable source content.

New governed artifacts

  • patch/direct-human-readable-wording-over-metaphor-heavy-shorthand.patch.md
  • patch/rules-first-over-memory-and-portable-support-artifacts.patch.md
  • phase/phase-022-01-refine-direct-human-readable-wording.md
  • phase/phase-022-02-sync-master-docs-and-runtime-install.md
  • phase/phase-023-01-rules-first-over-memory-boundary.md
  • phase/phase-023-02-sync-master-docs-and-runtime-install.md

Verification

  • master changelog anchor integrity passed
  • touched rule/design/changelog/master/phase/patch surfaces were synchronized
  • touched runtime rule copies were re-synced into ~/.claude/rules/
Assets 2
Loading