# ADR-0079: Ratify Feature Maturity and Release Governance

Status: Accepted\
Date: 2026-10-01\
Review Date: 2027-04-01

## Context

The [Feature Maturity and Release Governance policy](../../wepppy/weppcloud/routes/usersum/weppcloud/feature-maturity-and-release-governance.md) remained marked Draft. The project maintainer reported repeated requests for collaborator feedback with no response and explicitly requested ratification.

## Decision

Ratify the existing policy effective 2026-10-01. Preserve its substantive provisions and use its Policy Maintenance process for subsequent amendments. Lack of response is recorded as no feedback received, not collaborator approval or consensus.

## Authority and Decision Provenance

- Decision owner and authorizing principal: the project maintainer requesting ratification in the 2026-10-01 user-agent conversation.
- Authority path: explicit human maintainer instruction to the coding agent to record adoption; the agent implements the documentation change.
- Approval scope: adoption of this project-level governance policy.
- Consultation evidence: the maintainer's report that repeated requests received no feedback. Request dates, recipients, and correspondence were not supplied with this decision.

## Rationale

Adoption establishes an explicit release-governance baseline after repeated opportunities for feedback. Keeping the policy in draft indefinitely would leave its status unresolved. Later feedback can be evaluated through documented amendments.

## Alternatives Considered

1. Continue waiting for collaborator responses: rejected by the maintainer's decision to ratify after repeated unanswered requests.
2. Treat silence as unanimous consent: rejected because non-response does not establish endorsement.

## Consequences and Implementation Notes

The policy becomes the adopted project-level release framework. Ratification does not itself change registry entries, access grants, embargo dates, or feature maturity labels, and does not establish that all implementation requirements have been completed. Existing implementation gaps remain subject to the policy's Implementation Requirement section.

The policy's existing scope boundaries and amendment process remain in effect.

## Review

Set an initial policy review for 2027-04-01 to assess implementation experience and any subsequent collaborator feedback. Earlier substantive feedback may trigger an amendment proposal. This review date does not expire the policy; revisions or supersession should be documented with their authority and rationale.
