Skip to content

zrwangems/dsh-zrwang-plugin / ars/skills/sr-screener

sr-screener

Flagged

系统综述文献筛选:把方案或 PROSPERO 协议转成资格规则,双盲筛选标题摘要与全文,第三人裁决冲突,输出 PRISMA 2020 计数、EndNote/Zotero RIS 分组与可交付给论文技能的 literature_corpus。Triggers: systematic review screening, screen papers, PRISMA counts, pilot screening, adjudicate conflicts | 文献筛选, 系统综述筛选, PRISMA 计数, 筛选冲突裁决。

FileKindSize
SKILL.mdskill md33.1 KB
_shared/ARCHITECTURE.mdmarkdown51.7 KB
_shared/MODE_REGISTRY.mdmarkdown6.7 KB
_shared/agents/compliance_agent.mdmarkdown9.4 KB
_shared/artifact_reproducibility_pattern.mdmarkdown9.8 KB
_shared/benchmark_report.schema.jsonconfig2.7 KB
_shared/benchmark_report_pattern.mdmarkdown8.8 KB
_shared/bibliographic_integrity_signals.mdmarkdown8.1 KB
_shared/collaboration_depth_rubric.mdmarkdown11.5 KB
_shared/compliance_checkpoint_protocol.mdmarkdown8.9 KB
_shared/compliance_report.schema.jsonconfig8.1 KB
_shared/contracts/README.mdmarkdown54.7 KB
_shared/contracts/activity/adjudication_activity_input.schema.jsonconfig18.5 KB
_shared/contracts/activity/adjudication_activity_store.schema.jsonconfig18.7 KB
_shared/contracts/audit/audit_jsonl.schema.jsonconfig5.4 KB
_shared/contracts/audit/audit_sidecar.schema.jsonconfig8.4 KB
_shared/contracts/audit/audit_verdict.schema.jsonconfig5.4 KB
_shared/contracts/audit/cross_document_consistency_advisory.schema.jsonconfig20.4 KB
_shared/contracts/audit/cross_document_consistency_advisory_draft.schema.jsonconfig23.4 KB
_shared/contracts/audit/cross_document_source_manifest.schema.jsonconfig6.3 KB
_shared/contracts/audit/tortured_phrase_advisory.schema.jsonconfig30.9 KB
_shared/contracts/audit/tortured_phrase_snapshot.schema.jsonconfig4.9 KB
_shared/contracts/audit/tortured_phrase_snapshot_manifest.schema.jsonconfig7.3 KB
_shared/contracts/capability/stage_capability_matrix.jsonconfig23.5 KB
_shared/contracts/claim_standing/candidate_ledger.schema.jsonconfig23.1 KB
_shared/contracts/claim_standing/query_plan.schema.jsonconfig12.7 KB
_shared/contracts/claim_standing/query_plan_v1_1.schema.jsonconfig20.3 KB
_shared/contracts/claim_standing/retrieval_input.schema.jsonconfig14.4 KB
_shared/contracts/claim_standing/stance_record.schema.jsonconfig11.7 KB
_shared/contracts/claim_standing/transmission_ledger.schema.jsonconfig7.6 KB
_shared/contracts/cross_model/codex_citation_receipt.schema.jsonconfig4.7 KB
_shared/contracts/cross_model/codex_citation_request.schema.jsonconfig986 B
_shared/contracts/cross_model/promotion_bakeoff_sealed_commitment.schema.jsonconfig1.5 KB
_shared/contracts/cross_model/promotion_bakeoff_sealed_reveal.schema.jsonconfig1.5 KB
_shared/contracts/degradation_registry.jsonconfig42.5 KB
_shared/contracts/evaluator/full.jsonconfig6.3 KB
_shared/contracts/evidence/claim_registry.schema.jsonconfig2.3 KB
_shared/contracts/evidence/claim_registry_coverage_report.schema.jsonconfig4.8 KB
_shared/contracts/evidence/evidence_row.schema.jsonconfig14.3 KB
_shared/contracts/evidence/evidence_row_v1_1.schema.jsonconfig11.4 KB
_shared/contracts/evidence/evidence_row_v1_2.schema.jsonconfig21.8 KB
_shared/contracts/evidence/evidence_row_v1_3.schema.jsonconfig10.7 KB
_shared/contracts/human_subjects/authority_profile_registry.schema.jsonconfig16.7 KB
_shared/contracts/human_subjects/committee_correspondence.schema.jsonconfig9.9 KB
_shared/contracts/human_subjects/content_coverage_advisory.schema.jsonconfig19.9 KB
_shared/contracts/human_subjects/irb_context_record.schema.jsonconfig12.1 KB
_shared/contracts/human_subjects/resolved_authority_context.schema.jsonconfig11.8 KB
_shared/contracts/human_subjects/review_pathway_rule_trace.schema.jsonconfig9.5 KB
_shared/contracts/human_subjects/review_pathway_trace_request.schema.jsonconfig4.8 KB
_shared/contracts/human_subjects/submission_packet_inventory.schema.jsonconfig8.5 KB
_shared/contracts/human_subjects/submission_packet_manifest.schema.jsonconfig32.2 KB
_shared/contracts/passport/audit_artifact_entry.schema.jsonconfig10.8 KB
_shared/contracts/passport/bibliographic_integrity_signal.schema.jsonconfig48.9 KB
_shared/contracts/passport/citation_provenance.schema.jsonconfig4.8 KB
_shared/contracts/passport/citation_verification_summary.schema.jsonconfig8.2 KB
_shared/contracts/passport/claim_audit_result.schema.jsonconfig7.8 KB
_shared/contracts/passport/claim_drift.schema.jsonconfig3.8 KB
_shared/contracts/passport/claim_intent_manifest.schema.jsonconfig6.6 KB
_shared/contracts/passport/constraint_violation.schema.jsonconfig3.6 KB
_shared/contracts/passport/excluded_source_entry.schema.jsonconfig1.7 KB
_shared/contracts/passport/experiment_alignment_result.schema.jsonconfig4.8 KB
_shared/contracts/passport/experiment_provenance_entry.schema.jsonconfig10.0 KB
_shared/contracts/passport/human_read_log.schema.jsonconfig3.8 KB
_shared/contracts/passport/inquiry_ledger_ref.schema.jsonconfig881 B
_shared/contracts/passport/literature_corpus_entry.schema.jsonconfig30.3 KB
_shared/contracts/passport/preregistration_artifact.schema.jsonconfig4.3 KB
_shared/contracts/passport/rejection_log.schema.jsonconfig3.3 KB
_shared/contracts/passport/reset_ledger_entry.schema.jsonconfig7.1 KB
_shared/contracts/passport/run_ledger.schema.jsonconfig8.0 KB
_shared/contracts/passport/standing_constraint_entry.schema.jsonconfig2.6 KB
_shared/contracts/passport/temporal_audit_results.schema.jsonconfig8.8 KB
_shared/contracts/passport/terminal_policies.schema.jsonconfig8.1 KB
_shared/contracts/passport/timeline.schema.jsonconfig4.7 KB
_shared/contracts/passport/uncited_assertion.schema.jsonconfig3.3 KB
_shared/contracts/passport/uncited_audit_failure.schema.jsonconfig4.4 KB
_shared/contracts/passport/user_attested_read_resolution.schema.jsonconfig3.2 KB
_shared/contracts/passport/version_records.schema.jsonconfig4.9 KB
_shared/contracts/patch/block_manifest.schema.jsonconfig2.1 KB
_shared/contracts/patch/legacy/v1_0/revision_patch.schema.jsonconfig5.3 KB
_shared/contracts/patch/revision_patch.schema.jsonconfig8.9 KB
_shared/contracts/pdf/pdf_content_classifier_diagnostic.schema.jsonconfig1.2 KB
_shared/contracts/pdf/pdf_content_classifier_worker.schema.jsonconfig2.2 KB
_shared/contracts/pdf/pdf_read_preflight.schema.jsonconfig6.8 KB
_shared/contracts/re_review/input_manifest.schema.jsonconfig7.6 KB
_shared/contracts/re_review/legacy/v1_0/input_manifest.schema.jsonconfig6.2 KB
_shared/contracts/re_review/legacy/v1_0/precommitment.schema.jsonconfig8.9 KB
_shared/contracts/re_review/legacy/v1_0/traceability.schema.jsonconfig34.2 KB
_shared/contracts/re_review/legacy/v1_0/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/re_review/precommitment.schema.jsonconfig8.6 KB
_shared/contracts/re_review/traceability.schema.jsonconfig37.7 KB
_shared/contracts/re_review/verdict_record.schema.jsonconfig10.5 KB
_shared/contracts/research_workflow/inquiry_branch_ledger.schema.jsonconfig17.0 KB
_shared/contracts/research_workflow/research_workflow_profile.schema.jsonconfig7.2 KB
_shared/contracts/research_workflow/research_workflow_profile_selection_receipt.schema.jsonconfig3.9 KB
_shared/contracts/review_target/constructive_review_findings.schema.jsonconfig7.0 KB
_shared/contracts/review_target/criteria_registry.schema.jsonconfig4.0 KB
_shared/contracts/review_target/review_criteria_binding_manifest.schema.jsonconfig7.9 KB
_shared/contracts/review_target/review_criteria_source_receipt.schema.jsonconfig5.6 KB
_shared/contracts/review_target/review_target_context.schema.jsonconfig4.5 KB
_shared/contracts/review_target/review_target_declaration.schema.jsonconfig4.6 KB
_shared/contracts/reviewer/full.jsonconfig3.7 KB
_shared/contracts/reviewer/methodology_focus.jsonconfig2.2 KB
_shared/contracts/reviewer/review_panel_provenance.schema.jsonconfig7.8 KB
_shared/contracts/reviewer/review_panel_provenance_carrier.schema.jsonconfig4.1 KB
_shared/contracts/reviewer/review_panel_provenance_input.schema.jsonconfig3.5 KB
_shared/contracts/revision/author_adjudication.schema.jsonconfig7.8 KB
_shared/contracts/revision/author_adjudication_input.schema.jsonconfig1.2 KB
_shared/contracts/revision/claim_strength_drift_disposition.schema.jsonconfig3.6 KB
_shared/contracts/revision/claim_strength_drift_disposition_input.schema.jsonconfig3.1 KB
_shared/contracts/revision/claim_strength_drift_findings.schema.jsonconfig4.2 KB
_shared/contracts/revision/claim_surface_manifest.schema.jsonconfig3.3 KB
_shared/contracts/revision/integrity_correction_authorization.schema.jsonconfig4.3 KB
_shared/contracts/revision/integrity_correction_authorization_input.schema.jsonconfig1.5 KB
_shared/contracts/revision/integrity_correction_list.schema.jsonconfig1.8 KB
_shared/contracts/revision/integrity_pass_receipt.schema.jsonconfig809 B
_shared/contracts/revision/revision_evidence_bundle.schema.jsonconfig4.9 KB
_shared/contracts/revision/revision_roadmap.schema.jsonconfig11.2 KB
_shared/contracts/submission/format_profile.example.yamlconfig971 B
_shared/contracts/submission/format_profile.schema.jsonconfig4.6 KB
_shared/contracts/submission/submission_verification_report.schema.jsonconfig10.3 KB
_shared/contracts/submission/venue_profile.schema.jsonconfig4.1 KB
_shared/contracts/writer/full.jsonconfig3.6 KB
_shared/cross_model_verification.mdmarkdown83.3 KB
_shared/description-original.mdmarkdown1.1 KB
_shared/dsh-runtime.mdmarkdown1.5 KB
_shared/evals_lift_report.schema.jsonconfig5.0 KB
_shared/ground_truth_isolation_pattern.mdmarkdown16.0 KB
_shared/handoff_schemas.mdmarkdown96.9 KB
_shared/human_subjects_authority_registry.jsonconfig49.5 KB
_shared/mode_spectrum.mdmarkdown5.2 KB
_shared/model_tiering.mdmarkdown12.6 KB
_shared/output_language_pair.mdmarkdown7.7 KB
_shared/policy_data/nature_policy.mdmarkdown3.9 KB
_shared/prisma_trAIce_protocol.mdmarkdown10.2 KB
_shared/raise_framework.mdmarkdown7.5 KB
_shared/references/authority_content_coverage_advisory_protocol.mdmarkdown14.0 KB
_shared/references/claim_standing_candidate_ledger_protocol.mdmarkdown19.2 KB
_shared/references/claim_strength_ladder.mdmarkdown5.5 KB
_shared/references/cross_document_consistency_advisory_protocol.mdmarkdown13.5 KB
_shared/references/evidence_row_protocol.mdmarkdown14.4 KB
_shared/references/firm_rules.mdmarkdown11.0 KB
_shared/references/human_subjects_authority_protocol.mdmarkdown13.1 KB
_shared/references/intent_clarification_protocol.mdmarkdown11.9 KB
_shared/references/irb_terminology_glossary.mdmarkdown12.4 KB
_shared/references/per_source_method_weaknesses.mdmarkdown4.2 KB
_shared/references/protected_hedging_phrases.mdmarkdown8.9 KB
_shared/references/psychometric_terminology_glossary.mdmarkdown8.7 KB
_shared/references/review_criteria_consumer_protocol.mdmarkdown10.3 KB
_shared/references/review_form_note.mdmarkdown11.3 KB
_shared/references/review_pathway_rule_trace_protocol.mdmarkdown8.3 KB
_shared/references/routing_core.mdmarkdown5.7 KB
_shared/references/submission_packet_manifest_protocol.mdmarkdown13.6 KB
_shared/references/word_count_conventions.mdmarkdown9.0 KB
_shared/research_workflow_profiles/field_general.jsonconfig1.2 KB
_shared/review_criteria_registry.jsonconfig11.5 KB
_shared/review_criteria_sources/msr-2027-technical-papers.2026-08-24.jsonconfig2.0 KB
_shared/review_criteria_sources/sigsoft-empirical-standards.2026-08-24.jsonconfig1.4 KB
_shared/sprint_contract.schema.jsonconfig19.0 KB
_shared/style_calibration_protocol.mdmarkdown6.9 KB
_shared/templates/codex_audit_multifile_template.mdmarkdown16.7 KB
agents/protocol_architect_agent.mdmarkdown6.4 KB
agents/qc_auditor_agent.mdmarkdown5.2 KB
agents/reporter_agent.mdmarkdown3.7 KB
agents/screening_reviewer_agent.mdmarkdown5.4 KB
examples/example_config_dta.jsonconfig1.8 KB
examples/example_protocol_dta.mdmarkdown3.8 KB
examples/quick_screen_example.mdmarkdown3.0 KB
references/decision_rules.mdmarkdown6.7 KB
references/failure_paths.mdmarkdown4.1 KB
references/orchestration.mdmarkdown12.4 KB
references/protocol_template.mdmarkdown6.2 KB
references/quality_control.mdmarkdown6.0 KB
references/reporting_and_handoff.mdmarkdown5.8 KB
references/reviewer_roles.mdmarkdown4.0 KB
scripts/_claim_audit_constants.pyscript13.7 KB
scripts/_markdown_lint_util.pyscript9.0 KB
scripts/_next_verified_at_ms.pyscript6.5 KB
scripts/_skill_lint.pyscript13.6 KB
scripts/ars_cache_invalidate.pyscript1.3 KB
scripts/ars_mark_read.pyscript18.2 KB
scripts/ars_write_scope_guard.pyscript30.9 KB
scripts/audit_snapshot.pyscript23.5 KB
scripts/bibliographic_integrity_signals.pyscript32.2 KB
scripts/build_claim_standing_candidate_ledger.pyscript54.3 KB
scripts/build_claim_standing_query_plan.pyscript25.0 KB
scripts/build_content_coverage_advisory.pyscript45.1 KB
scripts/build_cross_document_consistency_advisory.pyscript77.9 KB
scripts/build_outputs.pyscript33.0 KB
scripts/build_review_pathway_rule_trace.pyscript34.2 KB
scripts/build_submission_packet_manifest.pyscript88.1 KB
scripts/build_workflow.pyscript20.0 KB
scripts/check_audit_artifact_consistency.pyscript103.9 KB
scripts/check_benchmark_report.pyscript2.4 KB
scripts/check_claim_audit_consistency.pyscript68.9 KB
scripts/check_claim_standing_freshness.pyscript9.7 KB
scripts/check_claim_standing_transmissions.pyscript17.9 KB
scripts/check_committee_correspondence.pyscript14.9 KB
scripts/check_corpus_consumer_protocol.pyscript13.7 KB
scripts/check_cross_model_handoff_contract.pyscript9.9 KB
scripts/check_data_access_level.pyscript5.2 KB

references/orchestration.md

View on GitHub
> 输出语言(本 DSH 集成强制):所有面向用户的文字、稿件、摘要、评审与报告一律使用**简体中文**;英文术语与引文保持英文。文中的 `zh-TW` / `zh-tw-en` 只是上游语言代码与脚本参数,不代表要用繁体输出。用户明确要求其他语言时以用户为准。
>
> 多角色执行(评审团、十阶段流水线、角色扮演)必须使用 DSH 的 Agent Team 工具(`spawn_teammate`、`team_task_*`、`wait_agent`、`send_message`);当前会话看不到这些工具,说明用户没开 Agent Team,必须先提示用户开启,不得退化成单会话顺序扮演。
# Running the pipeline

## Contents
1. Setup and the reviewer subagent
2. Paths: Workflow tool, Agent tool, single session
3. Cost and batch size
4. Resume after interruption
5. Mode recipes

## 1. Setup and the reviewer subagent

- **Plugin install** (skill + subagent): `/plugin marketplace add Imbad0202/academic-research-skills`,
  then `/plugin install academic-research-skills`. The reviewer subagent ships in the plugin's
  `agents/` folder and is listed with the plugin prefix:
  `academic-research-skills:screening-reviewer-agent`.
- **Skills-copy install** (the `sr-screener` folder symlinked or copied into `~/.claude/skills/`):
  also copy `../sr-screener/agents/screening_reviewer_agent.md` into `.claude/agents/` (this
  project) or `~/.claude/agents/` (all projects); it is then listed as `screening-reviewer-agent`.
- Put the exact agent name shown in the session's agent list into `agent_type` in
  `screening_config.json`. A wrong name makes every call fail at once, which the pilot shows
  immediately. An empty `agent_type` uses the default workflow subagent: it works, but it
  carries more tools and more overhead per call.
- Before #1037 the reviewer was named `screening_reviewer_agent`. A saved
  `academic-research-skills:screening_reviewer_agent` dispatches to the new plugin name. A bare
  `screening_reviewer_agent` is dispatched as written, because it names your own copy; after you
  copy the new agent file, change `agent_type` to `screening-reviewer-agent`. Changing between the
  two plugin names does not archive the decisions of a stage in progress; changing a bare name
  does, because the two names can be two different local files.
- Python 3.9+ runs the scripts; `pip install openpyxl` gives an Excel log instead of CSV files.

## 2. Paths

### Workflow tool (preferred at scale)

1. `build_workflow.py ta --jobs pilot|all|pending|recheck ...` writes a script under
   `<work>/runs/` and prints its path, job count, planned agent calls and models.
2. Show the user that estimate. The Workflow tool runs only when the user has opted into
   multi-agent orchestration; a request such as "run the screening workflow" is enough.
3. `Workflow({scriptPath: "<path>"})`. Each batch runs Reviewer A and Reviewer B in parallel,
   retries missing IDs with a Grep subset call, and sends advance-vs-exclude conflicts to the
   adjudicator in the same run.
4. When it finishes, merge: the journal sits at
   `~/.claude/projects/<project>/<session>/subagents/workflows/<runId>/journal.jsonl`. Pass that
   folder, or the whole `workflows` folder, to `merge_decisions.py --from`.
5. Never edit the generated script by hand; change `templates/prompts.md`, the protocol or the
   config and generate it again. Generated scripts are the audit trail of what each run used.

### Agent tool (no Workflow tool)

1. Add `--emit-prompts <work>/prompts` to `build_workflow.py`; it writes one prompt file per
   call and `index.json` (label, prompt file, model).
2. For each entry: an Agent call with the reviewer subagent and the prompt "Read the file
   <prompt_file> and follow its instructions exactly." Run a few at a time.
3. Save each returned JSON as `<work>/decisions/<label with : replaced by _>.json` holding
   `{"label": "<full label from index.json, including @context_id>", "decisions": [...]}`.
   The suffix ties the return to this review and protocol/config revision; do not remove it.
4. `merge_decisions.py --from <work>/decisions` reads the folder. Conflicts and missing IDs
   come back through `--jobs pending --emit-prompts ...` the same way.

### Single session (no subagents, for example claude.ai)

Only `quick` mode is honest here: one model reading a record twice is not two independent
reviewers. Screen small sets with the decision procedure in `references/reviewer_roles.md`, label the
result single-reviewer triage, and have a person act as the second reviewer.

## 3. Cost and batch size

- Agent calls for title/abstract screening: about 2 x batches, plus one adjudication call per
  batch with conflicts, plus retries. With 50 records per batch, 10,000 records mean roughly
  400-500 calls.
- Measure, do not guess: after the pilot, scale its token use by
  (total batches / pilot batches).
- Each call reads the protocol and rules (identical for every batch, placed first so providers
  can cache them) plus one batch file. Long protocols cost on every call; keep them focused.
- The default batch (50 records, at most 90,000 characters, lines wrapped at 150 characters)
  fits one Read call; the Read tool cuts very long lines, which is why lines are wrapped.
  Lower `max_records` if reviewers often return fewer decisions than records.
- Full text: two calls per report plus adjudications. Reports are long, so use the stronger
  model there (`FTA`/`FTB`) and expect far fewer calls than at title/abstract stage.

## 4. Resume after interruption

Usage limits, closed sessions and failed agents are normal on long runs:

1. `merge_decisions.py --from <all run folders>`: everything returned so far is kept; the
   earliest valid decision per record and role within the current review/revision wins.
   Bound results from other reviews or revisions are rejected even if batch and record IDs match.
2. `build_workflow.py ta --jobs pending` schedules only what is missing: whole batches when a
   reviewer never ran, ID subsets when a reviewer skipped records, and open conflicts. It checks
   the pilot gate whenever those jobs reach outside the batches recorded in `pilot_batches.json`.
   To finish an incomplete pilot, use `--jobs pilot --batches <pilot batches>`; pending jobs
   confined to those batches also remain available. Work folders from before pilot-batch
   recording must regenerate the pilot workflow to record its batches.
3. Repeat until the merge prints "complete". A record is never given a default label along the
   way.

## 5. Mode recipes

**protocol**: follow `agents/protocol_architect_agent.md`; ends with the user's confirmation.

**quick**: no scripts. Apply the decision procedure to each record and answer with the table in
`references/reviewer_roles.md`. Offer the full pipeline if more records follow.

**pilot**: `prepare_records.py`, then `build_workflow.py ta --jobs pilot` (a spread of batches
plus every seed batch; `--pilot-n` or `--batches` to change). The team labels the same records
independently in `pilot_labels.csv`. Workflow, `merge_decisions.py --pilot-labels
pilot_labels.csv`, then the QC Auditor's pilot report. Amend, re-pilot, and continue only when
every labelled record has been compared, the AI misses none of the records the team advanced,
and the user gives the go-ahead. The workflow generator records the selected batches in
`pilot_batches.json` so pilot retries can be distinguished from screening the remaining batches.

**ta-screen**: `build_workflow.py ta --jobs all`, which refuses to start without a passing
`pilot_check.json`; `--jobs pending` also checks this gate for jobs outside the pilot (the pilot
batches can stay in: their decisions are already merged, so rerunning them only costs a little).
Then merge, `--jobs pending` until screening is complete,
`--jobs recheck` for the required QC recheck of joint exclusions, merge again until it prints
"complete", `overrides.csv` for the team's decisions, `build_outputs.py`.

**ft-screen**: `prepare_fulltext.py --pdf-dir PDFS` (name PDFs by record ID when possible;
missing ones are "reports not retrieved"; pass the same `--config` used for title/abstract).
Preparation waits for every title/abstract screening, adjudication and QC decision. Write the full-text
protocol, then
`build_workflow.py ft --jobs all`, Workflow, `merge_decisions.py --stage ft`, `--jobs pending`
until complete, `build_outputs.py --stage ft`. A full-text merge or report also remains incomplete
while title/abstract decisions or QC rechecks are pending; it cannot produce final counts or methods text.
It also checks that the current advances equal retrieved plus not-retrieved, with no overlap or
duplicates. Changing a TA decision invalidates `ft_preparation.json`: prepare again, regenerate
the FT workflow and merge results for that retrieval revision before reporting.

### Review identity and protocol amendments

`prepare_records.py` creates a distinct review ID even when two reviews use identical record IDs.
The workflow builder registers a protocol/config/dataset revision in `review_state.json`. Agent
labels and emitted prompt indexes carry its `@context_id`; the merger checks this identity before
using any decision. `decision_audit.json` retains accepted and rejected results.

Configuration identity is specific to each stage: effective exclusion codes and prompt wording,
core criteria, A/B personas, that stage's role models and agent type. Title/abstract also binds
conflict policy, QC selection/policy and batch reading limits. Full text uses its own exclusion
codes when supplied, otherwise the title/abstract codes. Updating reporting fields (`model_labels`,
`review_title`, language flags or labels unused in prompts) preserves decisions and a passing pilot.
Preparation options (`seeds`, `batching`, `dedup`) do not reset an existing prepared dataset; actual
changes to prepared records or batch membership change its dataset identity. Full-text-only model
or code edits preserve title/abstract decisions and require a new full-text revision only.

After editing the confirmed protocol or screening settings, regenerate a pilot workflow on the recorded
batches. This archives the previous stage decisions, agreement and QC state in
`revision_history.json` and starts a new revision. Old exclusions cannot overrule new decisions.
Re-screen the current revision; review state is reset conservatively because an amendment can
change eligibility throughout the dataset. A merge can also activate the revision explicitly with
`--protocol <confirmed protocol>`; changed screening inputs without regeneration refuse to merge.

For an existing revision made with the older whole-config hash, first use the original unchanged
config to regenerate its workflow (or read/build outputs). This upgrades the identity while keeping
context IDs, decisions and pilot validity. If the old config has already changed, regeneration
refuses to clear decisions: restore the original config for the upgrade, then apply the edits.

Pilot scope stays fixed across retries/amendments. Widening it requires `--pilot-override
"<reason>"`; the override is recorded. Generated workflows reject runtime `screen`, `adj`,
`recheck` or FT `items` replacements: regenerate to change jobs and re-check the gate.
A passing `pilot_check.json` authorizes only its recorded revision and unchanged human-label file.

For work folders made before identities existed, first regenerate the workflow (or merge with
`--protocol`) to register the current revision. Verify old files belong to this review and protocol,
then explicitly import unbound files with `--legacy-import-reason "<reason>"`. The audit records
the reason; this flag never accepts a result already bound to another review/revision. Re-run the
human-label comparison before starting the remaining batches.

**adjudicate** (a human screening set with conflicts): export the conflicting records with
titles and abstracts (Rayyan or Covidence CSV/RIS), `prepare_records.py` into a new work
folder, `build_workflow.py ta --jobs recheck-all`, Workflow, `merge_decisions.py --audit`.
`audit_report.csv` holds an independent AI third opinion per record for the team to weigh; it
does not decide.
For a new audit work folder, explicitly record why the team requested an audit outside a pilot
with `--pilot-override "<reason>"` when generating `recheck-all`; the normal scope gate still applies.

**audit** (double-check exclusions): the same recipe on the excluded set.
`audit_report.csv` lists first the records the senior reviewer would advance.

**report**: `build_outputs.py` (and `--stage ft`), then the Reporter card.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall