You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document conditional cloud review and optional human review - #3
Cloud review now depends on actual severity, uncertainty, scope and cost; human developer review stays optional. Verified routine documentation, noncritical copy or pure style may skip a separate provider review with reason/evidence, but policy/security/agent/workflow documents cannot Skip. Bounded normal changes use Lite; signing, keys, authentication, recovery/backup, pairing, transactions, migrations, workflows, permissions, security dependencies/copy, cross-service/complex changes and unknown risk use Balanced.
Use the least-cost adequate authorized route, reuse valid exact-head/base coverage, make one initial review after stable checks and batch material fixes before necessary re-review. Independent coverage is needed only when an actual risk/finding requires it and an installed, authorized route/scope/budget exists. If scope, quota, cap or activation is unavailable, record unavailable and use another already-authorized adequate route or hold the applicable gate. Do not downgrade critical review, add paid retries/fallbacks or infer fresh allowance. Existing caps and historical balances do not activate a reviewer or grant budget; ordinary within-scope/allowance review does not need repeated permission.
Actual findings/dispositions, reviewed SHA/base/coverage and skipped/pending/unavailable results must be recorded. Required CI/status checks, substantive security concerns, native/device validation, product signoff and operation-specific signing/deployment/release authorization remain intact. Existing comment-only human CODEOWNERS suggestions remain optional and require no access grants.
Policy/docs/templates/agent instructions only: no runtime, workflow, R5 implementation, permission, secret, budget, merge or deployment change. No new provider request or paid review is claimed. Current recorded Copilot ready-PR automation, plus mobile every-push review, does not implement conditional triage; Markdown does not fix settings or install mobile reviewer #7049. Keep source preparation and installed automation status separate.
Historical receipts remain tied to exact original commits. Record current-head validation separately; skipped/unavailable review is not a clean review.
CONTRIBUTING.md's runtime security/mobile-error-contract paragraph and policy link remain unchanged; no running-service acceptance is inferred.
Current conditional-policy head: 772ff5cd4857d3f609e3934046e8263c8e30f72a. An existing cloud agent who did not author these policy edits independently reviewed the exact prepared patch (manifest SHA-256 a0bf37b7be612932af8911e329899178f7db123c6b66aa0cd2a492df108b6a5a); no blocking finding. This is cloud-agent source evidence, not a completed Copilot/Claude provider review or formal GitHub approval. Fresh exact-head CI evidence follows. Policies remain draft/unmerged and live GitHub rules are unchanged: administrator access is still needed to remove enforced human approval and implement conditional triggering. No ready transition or new provider/paid review was requested.
Fresh exact-head CI: Fresh exact-head compile/tests39733648153 passed all127 tests across6 suites. Source-readiness39733648060 passed current-source and history secret scans. This is source evidence, not deployed-service acceptance.
The owner has directed progressing the prepared SigningServer/Desktop source changes after actual optional-human configuration and applicable cloud review/required checks. No additional generic source approval is required; the existing GitHub administrator execution route remains missing. Service deployment and credential operations retain separate authorization.
antuz123
changed the title
Request Ben, Utkarsh, and Parsh on future SigningServer PRs
Document Copilot review process and default reviewer ownership
Oct 7, 2026
Cloud review-policy dependency check — 12 October 2026
Current source head cc1ec241c8b67c47ee9ffc2152e2d6cc485e9346 is unchanged; exact-head hosted CI is successful. Public GitHub permission read reports Ben=read, Parsh=read, Utkarsh=admin. Read access does not establish accepted CODEOWNERS write access. Keep this unapproved PR draft while the documented access dependency remains open; verify all intended owners before ready/merge. No invitation, role, review effort/quota, permission or branch-protection setting was changed. No fresh Copilot review was requested. Documentation review does not need native Mac testing, and no source-policy approval substitutes for app/Desktop/backend or release acceptance.
antuz123
changed the title
Document Copilot review process and default reviewer ownership
Document optional human reviewers and Copilot review process
Oct 22, 2026
antuz123
changed the title
Document optional human reviewers and Copilot review process
Document conditional cloud review and optional human review
Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloud review now depends on actual severity, uncertainty, scope and cost; human developer review stays optional. Verified routine documentation, noncritical copy or pure style may skip a separate provider review with reason/evidence, but policy/security/agent/workflow documents cannot Skip. Bounded normal changes use Lite; signing, keys, authentication, recovery/backup, pairing, transactions, migrations, workflows, permissions, security dependencies/copy, cross-service/complex changes and unknown risk use Balanced.
Use the least-cost adequate authorized route, reuse valid exact-head/base coverage, make one initial review after stable checks and batch material fixes before necessary re-review. Independent coverage is needed only when an actual risk/finding requires it and an installed, authorized route/scope/budget exists. If scope, quota, cap or activation is unavailable, record unavailable and use another already-authorized adequate route or hold the applicable gate. Do not downgrade critical review, add paid retries/fallbacks or infer fresh allowance. Existing caps and historical balances do not activate a reviewer or grant budget; ordinary within-scope/allowance review does not need repeated permission.
Actual findings/dispositions, reviewed SHA/base/coverage and skipped/pending/unavailable results must be recorded. Required CI/status checks, substantive security concerns, native/device validation, product signoff and operation-specific signing/deployment/release authorization remain intact. Existing comment-only human CODEOWNERS suggestions remain optional and require no access grants.
Policy/docs/templates/agent instructions only: no runtime, workflow, R5 implementation, permission, secret, budget, merge or deployment change. No new provider request or paid review is claimed. Current recorded Copilot ready-PR automation, plus mobile every-push review, does not implement conditional triage; Markdown does not fix settings or install mobile reviewer #7049. Keep source preparation and installed automation status separate.
Historical receipts remain tied to exact original commits. Record current-head validation separately; skipped/unavailable review is not a clean review.
CONTRIBUTING.md's runtime security/mobile-error-contract paragraph and policy link remain unchanged; no running-service acceptance is inferred.
Current conditional-policy head:
772ff5cd4857d3f609e3934046e8263c8e30f72a. An existing cloud agent who did not author these policy edits independently reviewed the exact prepared patch (manifest SHA-256a0bf37b7be612932af8911e329899178f7db123c6b66aa0cd2a492df108b6a5a); no blocking finding. This is cloud-agent source evidence, not a completed Copilot/Claude provider review or formal GitHub approval. Fresh exact-head CI evidence follows. Policies remain draft/unmerged and live GitHub rules are unchanged: administrator access is still needed to remove enforced human approval and implement conditional triggering. No ready transition or new provider/paid review was requested.Fresh exact-head CI: Fresh exact-head compile/tests39733648153 passed all127 tests across6 suites. Source-readiness39733648060 passed current-source and history secret scans. This is source evidence, not deployed-service acceptance.
The owner has directed progressing the prepared SigningServer/Desktop source changes after actual optional-human configuration and applicable cloud review/required checks. No additional generic source approval is required; the existing GitHub administrator execution route remains missing. Service deployment and credential operations retain separate authorization.