Maintainers

The current maintainer of Kilolock and their scope of authority. Governance is intentionally minimal at the v0 stage: a single benevolent-dictator maintainer makes final decisions. This will be revisited as the project grows additional active contributors.

Current maintainers

Maintainer responsibilities

The maintainer is responsible for:

• Reviewing and merging Pull Requests.
• Cutting releases and tagging versions.
• Maintaining the roadmap and accepting,

  deferring, or declining proposed work.

• Enforcing the Code of Conduct.
• Responding to security reports (see

  CONTRIBUTING.md).

• Custodianship of the project's trademark

  (TRADEMARK.md) and CLA archive

  (cla/icla.md).

Decision-making

For technical decisions, the maintainer takes informal community input and decides. Major architectural decisions are recorded as ADRs in [docs/adr/](./docs/adr/) before they are implemented.

For licensing, trademark, and governance decisions, the maintainer decides, subject to the constraints of ADR 0003:

• The OSS license commitment (Apache 2.0) cannot be revoked.
• A future commercial entity may be formed and assigned project

  stewardship, but the OSS commitment survives the assignment.

Becoming a maintainer

When a second maintainer is added, this document and the associated governance ADR will be updated to reflect a more formal model (decision quorum, areas of responsibility, etc.). Until then, sustained high-quality contributions and engagement with project direction are the natural path to maintainership; reach out to the current maintainer to discuss.