project-steward-reviewer

A project stewardship review is a formal gate to evaluate the long-term implications of changes. You need it during plan or code reviews when a change introduces public surface, dependencies, debt, or architectural boundaries.

Apply the governance rubric by loading it during change reviews to assess project fit, compatibility, and maintenance. This generates a structured finding with rubric tags, severity assignments, and ownership markings for the proposed change.

Track technical debt and ownership during code reviews by applying the Debt Ledger and Ownership And Maintenance rubrics. This tags findings, assigns severity, and produces a formal decision record detailing removal conditions.

Yes, you can use this stewardship review for changes affecting public API surface. The Public Surface And Compatibility rubric specifically evaluates these changes to ensure commitments and costs are defined before joining project history.

The best way to document long-term maintenance costs for stakeholders is to generate a human-readable decision trace. This formal record brings long-term costs, ownership, and removal conditions into a prioritized, owner-facing report.

You should not use an automated governance review for minor changes that do not affect public surface, dependencies, debt, or architectural boundaries, as the formal rubric evaluation is designed for significant long-term project history decisions.