REPOSITORY AUTHORIZATION

Permission must precede acquisition.

This authorization is separate from identity, payment, and product entitlement. It governs when Seal of Sigmund may request and assess repository material.

VERSION: repository-authorization-v1
EFFECTIVE: 30 August 2026

1. Your authority

You confirm that the organization owns the selected repository or has explicit permission to authorize this security assessment. Do not connect third-party source merely because your GitHub identity can view it.

2. GitHub App boundary

Repository selection occurs in GitHub. Seal of Sigmund verifies the exact GitHub App, installation, account, permissions, repository identity, and visibility before sanitized metadata becomes active. A user OAuth token is not retained as standing repository authority.

3. Per-scan approval

Before acquisition, the service resolves and displays the default branch and immutable commit. Organization confirmation authorizes one bounded job for that exact repository, application root, commit, and purpose. Authority expires quickly and is not reusable for another target.

4. Processing limits

The archive enters an isolated, credential-empty, network-denied analysis path. Repository code is not executed. Source exists only for the bounded acquisition and scan operation; the admitted durable artifact is a reduced encrypted receipt.

5. Revocation

Disconnecting in Seal disables local metadata and schedules it for purge. It does not uninstall the GitHub App; uninstalling or changing repository selection remains a separate action in GitHub. Revocation does not erase audit or billing records that must be retained.

6. Honest failure

If identity, tenant, installation, commit, archive, or custody verification fails, the job aborts. A limited parser or recipe failure may instead produce an admitted receipt marked incomplete, with the failed coverage visible.