Skip to content

Maintainer Handbook

bijux-proteomics-maintain is the repository-health handbook. It explains how the repository keeps its promises alive: docs stay buildable, schemas stay checked, releases stay guarded, and shared commands stay understandable.

Product packages carry the scientific and operational ideas. This handbook carries the discipline that stops those ideas from decaying into folklore.

flowchart TB
    dev["bijux-proteomics-dev<br/>helper code"]
    makes["make system<br/>shared command surface"]
    workflows["github workflows<br/>automation and publication"]
    contracts["apis, docs, releases,<br/>package verification"]
    packages["product packages"]

    dev --> contracts
    makes --> contracts
    workflows --> contracts
    contracts --> packages

What This Handbook Makes Visible

  • where repository rules are executable instead of merely stated
  • how local commands, CI, and release automation reinforce each other
  • why a multi-package repository can stay coherent over time

Start With

  • open bijux-proteomics-dev when the rule is implemented as checked-in Python maintainer code
  • open gh-workflows when the symptom starts from GitHub automation
  • open makes when the question starts from make, CI target routing, or release command fan-out

What This Handbook Owns

  • repository-wide proof, publication, docs integrity, security, and policy enforcement
  • shared command routing and GitHub automation contracts
  • the boundary between package handbooks and repository-health surfaces

What It Should Never Become

  • a substitute for product-package documentation
  • a vague collection of release reminders
  • a place where automation hides without naming its real owner

First Proof Check

  • packages/bijux-proteomics-dev/src/bijux_proteomics_dev/
  • .github/workflows/
  • Makefile and makes/