Skip to content

Create weekly review batches, contributor intake, and monitoring #28

Open

Description

@advaitmb

The review-batch workflows and isolated live collector are ready; recurring operation remains disabled. PR #35 updates the evidence and handoff. Updated September 10, 2026.

  • Provide GitHub submission forms and durable approve/edit/reject/defer decisions.
  • Implement one continuing draft review PR, checks, artifacts, daily health checks, and an independent read-only monitor command.
  • Confirm primary maintainer: advaitmb.
  • Verify nine-member live collection, membership screening, repeat stability, and provider budget under Implement publication discovery, normalization, and deduplication #27.
  • Confirm backup reviewer or explicit sole-maintainer policy, plus failure-alert destination. A follow-up question is pending; no backup or destination has been invented.
  • Configure required website checks and the agreed human-review safeguard on master. Existing protection has no required checks or required PR reviews.
  • Enable the file gate and WEBSITE_MAINTENANCE_ENABLED after safeguards and the infrastructure merge are complete. Both stay off.
  • Connect a lab-owned independent missed-run monitor and verify failure notifications.
  • Complete two actual weekly cycles, recording missed papers, false matches, duplicates, recovery, and reviewer effort.

Automatic publication remains out of scope. Immediate pilot reruns do not satisfy the two-week requirement, and same-repository daily health checks are not independent monitoring.

Evidence: pilot / weekly log, runbook.

Activity

  1. advaitmb commented on Sep 9, 2026

    @advaitmb
    ContributorAuthor

    Activation audit — September 9, 2026\n\nThe recurring workflows exist and Actions has write permission with pull-request approval enabled, but both maintenance gates remain off: maintenance/config.json has enabled=false and no WEBSITE_MAINTENANCE_ENABLED repository variable is set. There are no repository rulesets, and master currently has no required status checks or required pull-request review configured.\n\nDo not activate the weekly collector yet. Before activation, name the primary/backup reviewers and notification destination, require review plus the check workflow on master, then enable the file gate and repository variable in a reviewed change. An independent missed-run monitor and two observed weekly cycles still remain after that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions