Skip to content

GOVERNANCE.adoc

Latest commit

 

History

History
125 lines (90 loc) · 3.87 KB

GOVERNANCE.adoc

File metadata and controls

125 lines (90 loc) · 3.87 KB
Raw

Governance Model

This document describes the governance model for the 0patch-lsa-sentinel repository.

Table of Contents

Overview

This repository follows a Benevolent Dictator (BDFL) Governance Model:

  • A single champion (@hyperpolymath) holds the project’s vision and final decision authority, while actively welcoming contributions and delegating.

  • Current reality: the project is presently staffed by a sole maintainer. That is a staffing fact, not a closed door — contributions are welcome and reviewed, and authority is delegable to anyone who demonstrably carries the project’s essence.

  • Decisions are made transparently through GitHub issues and discussions.

  • The project adheres to the hyperpolymath estate policies where applicable.

Core Principles

Principle Description

Benevolent Dictatorship

Maintainer has final decision authority but seeks community input

Meritocracy

Contributions are judged on technical merit, not contributor identity

Transparency

All significant decisions are documented publicly

Consensus-Seeking

Maintainer prefers consensus but will decide when necessary

Open Contribution

Anyone can contribute via fork and pull request

Roles and Permissions

Role Permissions Assignment

Maintainer

Write access, merge rights, admin

@hyperpolymath

Contributors

Read access, fork, submit PRs

All GitHub users

Users

Use the software, report issues

All GitHub users

Decision Making Framework

Routine Decisions

Bug fixes, documentation improvements, minor feature additions, dependency updates.

Process: Maintainer reviews and merges PRs that meet quality standards.

Significant Changes

New major features, ABI/FFI changes, architecture modifications, breaking changes.

Process:

  1. Open issue describing the change

  2. Discuss with community (minimum 72 hours)

  3. Maintainer makes final decision

  4. Document rationale in issue/PR

Structural Decisions

Repository purpose/renaming, license changes, ownership transfer, deprecation/archival.

Process:

  1. Extended discussion (minimum 1 week)

  2. Maintainer makes final decision

  3. Document in CHANGELOG and governance docs

Conflict Resolution

  1. Discuss in the relevant GitHub issue or PR

  2. Provide technical justification for positions

  3. Maintainer mediates and makes final decision

  4. Decision is documented and can be revisited later

Project Policies

This repository adheres to hyperpolymath estate-wide policies:

Repository-Specific Conventions

Convention Description

Signing

All commits must be signed (SSH or GPG)

SPDX Headers

All source files must carry SPDX license identifiers

Multi-language proof

The classifier verdict is SPARK-proved and cross-checked across Rust, Idris2, and Zig

Contractiles

Mustfile, Dustfile, Trustfile in .machine_readable/contractiles/

Machine Readable

descriptiles in .machine_readable/descriptiles/

CI/CD

GitHub Actions workflows in .github/workflows/

Changelog

Date Change By

2026-07-02

Initial governance model established

@hyperpolymath