template-proposal-review

To review upstream template proposals safely, evaluate draft proposals in the proposals/draft directory against evidence-based criteria, then move accepted items to the upstream repository using structured application steps. This ensures reproducible proposal handling and strict separation of concerns.

Cross-project template governance is managed by organizing proposals into structured directories covering draft, accepted, rejected, and applied statuses. This workflow guides maintainers through evidence-based decisions and reproducible status transitions for safe upstream application.

Localdocs ADRs and worklogs provide the evidence-based criteria needed to evaluate cross-project applicability of template proposals. Maintainers reference these localdocs records to make informed, reproducible decisions when reviewing draft proposals for upstream acceptance.

Yes, accepted proposals can be optionally applied to the upstream python-project-template repository. The process involves moving accepted proposals to the applied status folder and executing safe application steps to update the upstream template.

Yes, strict separation of concerns is required for template management proposal review. This principle ensures reproducible proposal handling, preventing cross-contamination between draft, accepted, rejected, and applied statuses during the governance workflow.

Manual proposal review risks inconsistent decisions and unsafe upstream application if not following structured governance. Without evidence-based criteria from localdocs ADRs and worklogs, maintaining reproducible cross-project template updates becomes error-prone and difficult to track.