Skip to content

Maintainer Handbook

Use this handbook when the question is about repository health, release alignment, or documentation stewardship rather than runtime product use.

These pages are public on purpose. This repository now publishes enough runtime and evidence depth that release stewardship is part of the public trust surface, not a private afterthought.

flowchart TD
    A[Repository change] --> B[Public docs]
    A --> C[Package metadata and READMEs]
    A --> D[Evidence and trust guides]
    A --> E[Release and quality reports]
    B --> F[Maintainer review]
    C --> F
    D --> F
    E --> F

What Maintainers Are Responsible For

  • keeping public docs, package READMEs, and metadata aligned with the actual runtime surface
  • preserving the boundary between native ownership, wrapper orchestration, and evidence closure
  • keeping release narratives truthful across documentation and governed readiness reports
  • preventing root clutter and unmanaged artifact drift

Stewardship Loop

flowchart LR
    A[Runtime or evidence change] --> B[Public docs and README review]
    B --> C[Quality and release review]
    C --> D[Publishable repository state]

What This Handbook Helps Prevent

  • public pages that understate the runtime depth now present in the code and tests
  • native surfaces that appear in code but disappear from package READMEs or release guidance
  • evidence-book pages that sound conclusive when the governed study record is still bounded
  • repository runs that leave unmanaged root artifacts behind

Handbook Sections

  • Documentation system for documentation ownership and native surface documentation rules
  • Trust surfaces for public trust surface maintenance, public interface and artifact maintenance, and trust lane and study guide maintenance
  • Repository operations for artifact hygiene and release surface alignment

Start With

  • Open Documentation system when the question is how public docs, package READMEs, and flagship native surfaces should be described together.
  • Open Trust surfaces when the concern is whether architecture, evidence-book, interface, and validation pages still tell one bounded public story.
  • Open Repository operations when the question begins with artifact hygiene, release alignment, or repository execution discipline.

Boundary

This handbook exists for repository stewardship, not product semantics. When a maintainer rule only wraps a runtime surface, this handbook should stop at the integration point and send the reader back to the owning product page.

For maintainers scanning by keyword, this handbook explicitly covers documentation ownership, native surface documentation, public trust surface maintenance, public interface and artifact maintenance, trust lane and study guide maintenance, artifact hygiene, and release surface alignment.

The maintained review vocabulary in this handbook includes these exact surface names because they are part of the repository's checked-in trust contract:

  • public trust surface maintenance
  • trust lane and study guide maintenance