REQ 100

REQ-100: Adoptable by forks and consumers without engine changes

Requirement

The gate shall ship as a versioned reusable workflow, a submission tool, and a readiness check, with no reviewer, repository, or organization name in engine code, so that each adopting repository configures its own environments and reviewers.

Rationale

The operator wants one mechanism for the organization and every fork, and REQ-001 forbids consumer identifiers in engine code. On Free, Pro, and Team plans, required reviewers and environment secrets exist only for public repositories. Rollout starts with an advisory no-op pilot in the fork, then enforces wiki publishing (decision D2 in VITechnologies/projectbuddy#177).

Fit Criterion

In a fresh public fork with no configuration, the readiness check names each missing setting and every request fails closed. After the documented setup, a no-op known-answer action class completes both the approve path and the reject path. A repository whose plan lacks required reviewers is reported as unsupported.

Verification

Planned, TEST-102; not yet performed live. Offline fixture tests report each missing setting as not ready, a private repository without required reviewers as unsupported, and drift tests tie the procedure to the code. Live verification waits for Phase 3 of VITechnologies/projectbuddy#179.

Source

Software-Requirements-Specification

Priority

High

TestID

TEST-102

TestArtifact

scripts/tests/test_approval_gate_docs.py drift tests and scripts/tests/test_approval_gate_record.py readiness cases

CodeRef

docs/approval-gate/procedure.md, docs/approval-gate/classes.example.json, scripts/approval_gate/readiness.py, .github/workflows/approval-request.yml

Status

Planned; offline fixture tests pass, no live proof yet