Status: FAIL_CLOSED / PLAN_BLOCKED / NO_GO

Repository: fscfede-beep/rumbo-control-queue
Repository ID: 1314199389
Owner: fscfede-beep
Owner ID: 293577326
Visibility: private

The authenticated GitHub identity is the repository owner and the connected integration reports repository permissions: admin, maintain, pull, push and triage are all true.

Request:

GET /repos/fscfede-beep/rumbo-control-queue/branches/main/protection

Observed:

HTTP 403

Message:

Resource not accessible by integration

Interpretation: this does not prove that native branch protection exists. Under the current integration it cannot be inspected, so branch protection remains unproven and cannot satisfy the R2 native-enforcement gate.

Request:

GET /repos/fscfede-beep/rumbo-control-queue/rulesets

Observed:

HTTP 403

Message:

Upgrade to GitHub Pro or make this repository public to enable this feature.

Interpretation: private-repository rulesets are unavailable on the current plan.

GitHub's current documentation states that protected branches and repository rulesets are available for public repositories on GitHub Free and for private repositories on GitHub Pro, Team and Enterprise. GitHub Pro also lists advanced private-repository tools such as required PR reviewers and protected branches.

Therefore the required native private-repository enforcement cannot honestly be marked PASS on the current plan.

No workaround has been applied:

• repository made public: NO
• paid GitHub plan purchased: NO
• native enforcement claimed without evidence: NO
• external authorizer substituted for native enforcement: NO

The external observer, authorizer and deployer remain defense-in-depth controls, but are not treated as equivalent to GitHub-native prevention of direct owner-side mutation.

Decision:

NATIVE_PRIVATE_REPOSITORY_RULESET_OR_BRANCH_ENFORCEMENT = BLOCKED

main_write_prevention_proven = false

merge_authorization_enabled = false

deploy_enabled = false

product_production = NO_GO

production_go = false