Files
stoned-ai/docs/00-GOVERNANCE-RULES.md
Jason Hall fcd93ee0af Initialize project governance and baseline structure
Stoned.AI — live-streamed human + AI conversation show, both sides voiced
via local Kokoro TTS. Governance docs 00-09, README, .gitignore.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-12 21:55:46 +00:00

1.5 KiB

Governance Rules

Core Rule

The documents in this project set the governing plan for the project.

They are never to be rewritten by implementation models unless:

  • the user explicitly requests a revision
  • a supervisor model proposes a revision
  • the user accepts the revision

Allowed Editors

The following may change governing documents:

  • the user
  • a supervisor model acting under explicit user direction

The following may not change governing documents without approval:

  • local coding models
  • implementation agents
  • documentation drafting agents
  • background automation

Allowed Actions For Implementation Models

  • read governing docs
  • restate requirements
  • create implementation artifacts
  • create subordinate notes
  • create code and tests
  • create proposed change requests

Forbidden Actions For Implementation Models

  • change project scope
  • weaken constraints
  • redefine acceptance criteria
  • override architecture decisions
  • silently reinterpret requirements

Revision Process

If implementation reveals the plan is wrong or incomplete:

  1. create a change request using 08-CHANGE-REQUEST.md
  2. stop changing the governing plan directly
  3. escalate the change request to the user or a supervisor model
  4. revise governing docs only after approval

Decision Authority

  • Primary Stakeholder: Jason
  • Supervisor: Claude (planning, architecture, review)
  • Workhorse: Implementation model (code, tests, scaffolding)
  • Reviewer: Claude or a second model comparing implementation to docs