Files
MokoSuiteClient/GOVERNANCE.md
T
Jonathan Miller 5e33f94cce
Platform: moko-platform CI / Gate 2: Unit Tests (8.1) (push) Has been cancelled
Platform: moko-platform CI / Gate 2: Unit Tests (8.2) (push) Has been cancelled
Platform: moko-platform CI / Gate 2: Unit Tests (8.3) (push) Has been cancelled
Platform: moko-platform CI / Gate 3: Self-Health Check (push) Has been cancelled
Platform: moko-platform CI / Gate 4: Governance (push) Has been cancelled
Platform: moko-platform CI / Gate 5: Template Integrity (push) Has been cancelled
Platform: moko-platform CI / CI Summary (push) Has been cancelled
Generic: Repo Health / Scripts governance (push) Has been cancelled
Generic: Repo Health / Repository health (push) Has been cancelled
Generic: Repo Health / Report Issues (push) Has been cancelled
Generic: Repo Health / Site Health (push) Has been cancelled
Generic: Repo Health / Access control (push) Has been cancelled
Universal: Auto Version Bump / Version Bump (push) Has been cancelled
Platform: moko-platform CI / Gate 1: Code Quality (push) Has been cancelled
chore: bump version to 02.34.16-dev, update updates.xml
Authored-by: Moko Consulting
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-06-06 08:08:45 -05:00

4.5 KiB

MokoStandards

Project Governance

Overview

This document defines the governance model for the MokoWaaSBrand repository within the mokoconsulting-tech organization. It is automatically maintained by MokoStandards v04.00.04.

Full governance policy is defined in the MokoStandards source repository: docs/policy/GOVERNANCE.md


Roles and Responsibilities

Maintainer

GitHub: @mokoconsulting-tech

Authority: Final decision-making authority on all matters for this repository.

Responsibilities:

  • Review and merge pull requests
  • Maintain code quality and standards compliance
  • Manage releases and versioning
  • Respond to issues and security reports

Contributors

Authority: Submit changes via pull requests.

Requirements:

  • Read and accept CODE_OF_CONDUCT.md
  • Follow CONTRIBUTING.md guidelines

Decision-Making

All changes must be submitted as pull requests. The maintainer (@mokoconsulting-tech) reviews and approves all changes before they are merged.

Sole Operator Policy

This organization operates under a sole operator model. The maintainer (@mokoconsulting-tech) is the sole employee and owner and may self-approve pull requests when no second reviewer is available. The following requirements remain mandatory regardless:

  1. Pull Requests Required — all changes to protected branches go through a PR.
  2. Automated Checks — all CI checks must pass before merging.
  3. Audit Trail — issues, pull requests, and commit history are preserved.
  4. Documentation — changes are documented in CHANGELOG.md.

See the full policy: Sole Operator Policy


Change Management

Change Type Approval Process
Routine (docs, bug fixes) Maintainer PR → CI pass → merge
Significant (new features) Maintainer PR with description → CI pass → merge
Major (breaking, architecture) Maintainer Issue discussion → PR → CI pass → merge
Emergency (security) Maintainer Labelled EMERGENCY → immediate merge → post-mortem

Reporting Issues


Metadata

Field Value
Document Type Policy
Domain Governance
Applies To mokoconsulting-tech/MokoWaaSBrand
Jurisdiction Tennessee, USA
Maintainer @mokoconsulting-tech
Standards MokoStandards v04.00.04
Repo https://github.com/mokoconsulting-tech/MokoWaaSBrand
Path /GOVERNANCE.md
Status Active — auto-maintained by MokoStandards