Skip to content

zrwangems/dsh-zrwang-plugin / ars/skills/academic-paper

academic-paper

Flagged

学术论文写作:按 IMRaD 或领域结构成稿,含大纲、论证地图、双语摘要、图表与题注、引用格式转换、返修与逐条回复、AI 使用声明。Triggers: write a paper, academic paper, paper outline, revise paper, reviewer comments, rebuttal, citation check, abstract | 写论文, 论文大纲, 修改论文, 审稿意见, 返修, 审稿回复, 引文核对, 写摘要。

FileKindSize
SKILL.mdskill md65.4 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.2 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/abstract_bilingual_agent.mdmarkdown12.5 KB
agents/argument_builder_agent.mdmarkdown11.5 KB
agents/citation_compliance_agent.mdmarkdown27.0 KB
agents/draft_writer_agent.mdmarkdown57.1 KB
agents/formatter_agent.mdmarkdown64.5 KB
agents/intake_agent.mdmarkdown26.1 KB
agents/literature_strategist_agent.mdmarkdown47.2 KB
agents/peer_reviewer_agent.mdmarkdown30.5 KB
agents/revision_coach_agent.mdmarkdown20.6 KB
agents/socratic_mentor_agent.mdmarkdown28.5 KB
agents/structure_architect_agent.mdmarkdown19.5 KB
agents/visualization_agent.mdmarkdown17.8 KB
examples/chinese_paper_example.mdmarkdown21.1 KB
examples/clinical_citation_verification_checklist.mdmarkdown4.4 KB
examples/clinical_epistemic_status_example.mdmarkdown6.6 KB
examples/commitment_ledger_example.mdmarkdown8.1 KB
examples/imrad_hei_example.mdmarkdown23.3 KB
examples/literature_review_example.mdmarkdown30.8 KB
examples/plan_mode_guided_writing.mdmarkdown34.3 KB
examples/revision_mode_example.mdmarkdown20.1 KB
examples/revision_recovery_example.mdmarkdown41.2 KB
examples/version_family_reconciliation_example.mdmarkdown3.8 KB
references/abstract_writing_guide.mdmarkdown13.2 KB
references/academic_writing_style.mdmarkdown8.2 KB
references/anti_leakage_protocol.mdmarkdown5.0 KB
references/apa7_chinese_citation_guide.mdmarkdown14.6 KB
references/apa7_extended_guide.mdmarkdown7.2 KB
references/changelog.mdmarkdown3.4 KB
references/citation_format_switcher.mdmarkdown8.0 KB
references/committee_correspondence_protocol.mdmarkdown7.0 KB
references/credit_authorship_guide.mdmarkdown14.3 KB
references/disclosure_mode_protocol.mdmarkdown54.5 KB
references/domain_evidence_profiles.mdmarkdown4.8 KB
references/failure_paths.mdmarkdown14.9 KB
references/funding_statement_guide.mdmarkdown12.5 KB
references/hei_domain_glossary.mdmarkdown7.4 KB
references/intro_title_rhetoric_guide.mdmarkdown9.3 KB
references/journal_submission_guide.mdmarkdown9.3 KB
references/latex_template_reference.mdmarkdown10.3 KB
references/mode_selection_guide.mdmarkdown18.3 KB

_shared/references/claim_standing_candidate_ledger_protocol.md

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

Status: Track A offline substrate, live discovery adapters, stance-side contracts, the stance runner (injected-transport only), the semantic stance-record validator, the deterministic presentation renderer, and the pipeline wiring (consent-surface builder, freshness checker, transmission ledger) implemented; the relevance assessor, a live stance-provider adapter, and claim-standing measurement remain unimplemented.

This protocol fixes the deterministic boundary between a consent-bound search plan, already-retained adapter-neutral retrieval records, and a candidate ledger. It does not retrieve records, call a model, infer stance, render claim standing, or dispatch a held-out evaluation.

## Contract identities

- `claim-standing-query-plan/1.0`: the frozen checkpoint, tier rule, query/index envelope, caps, and consent receipt.
- `claim-standing-retrieval-input/1.0`: explicit attempts, retained raw hits, caller-supplied relevance assessments bound to exact claim/candidate/prompt bytes, and a whole-input digest.
- `claim-standing-candidate-ledger/1.0`: an auditable terminal state for every attempt and raw hit plus deterministic work-family selection.
- `claim-standing-query-plan/1.1`: the stance-authorizable consent — identical to 1.0 except the decision may be `retrieval_plus_stance`, binding a top-level `stance_plan` (exact provider/model, prompt contract, retention disclosure) by hash and extending the authorized content classes by exactly the stance transmission class. The validator accepts both versions; 1.0 semantics are unchanged.
- `claim-standing-stance-record/1.0`: the future stance runner's output contract — §7 probe-identity hashes, per-family rows under the closed §5.1 vocabulary with mandatory evidence-row references, the all-selected distribution, and the mandatory `STANCE CLASSIFICATION UNMEASURED` banner. `scripts/claim_standing_stance_runner.py` implements the runner against an injected transport whose declared identity must equal the consented `stance_plan` (no live provider adapter exists; its CLI refuses until one ships with its own consent surface), and `validate_stance_record` is the required semantic verifier (identity hashes, distribution sum, exact selected-family coverage, per-evidence-row hash replay). Each transport call is recorded as a transmission event (recipient, purpose, content classes, prompt hash/bytes, consent receipt, retention disclosure, result state) returned beside the record; `claim-standing-transmission-ledger/1.0` below is the dedicated contract those events land in. `scripts/render_claim_standing_view.py` renders the §5.3 three-part view with the §5.4 bounded vocabulary, fixed empty wording, all-selected denominator, inert escaping of provider text, and stale-record refusal.
- `claim-standing-transmission-ledger/1.0`: the design §6 per-event accounting of every authorized transmission attempt in one probe. Retrieval-query events derive one-to-one from the retained attempts (recipient index and product identity, `scholarly_discovery` purpose, the `accepted_search_query` content class, query hash and UTF-8 byte count, consent receipt, retention disclosure, attempt start time, and the closed attempt-outcome vocabulary as result state); stance-classification events are the runner's transmission records copied field-for-field, with any unexpected field refused. Accounting is deliberately conservative: an attempt an adapter refused before transport still appears with its failure result state, so the ledger may overstate, never understate, what could have left the session, and byte counts are of the consented content class (accepted query text / exact prompt), not transport framing. `scripts/check_claim_standing_transmissions.py` is the normative builder/validator and the §9 gate-14 check. It first schema-validates the plan and retrieval input and replays both self-digests (a silently edited attempt list cannot be accounted), then fails closed on: an event whose content classes fall outside the plan's authorized allowlist; a recipient outside the consented roster or `stance_plan`; an attempt naming an index that is not a consented target of its query; a duplicate attempt id (double-counted event); a consent-receipt or retention-disclosure drift; an unrecorded result state; and stance transmissions under a plan that does not authorize them. A `retrieval_plus_stance` plan must supply its stance transmissions explicitly — an empty list is an explicit assertion that no stance call ran — and passing the stance record cross-checks that every row that reached the transport has its event (only an `abstract_missing` row never builds a prompt). Completeness for a run interrupted before the runner returned its transmission list remains caller-honesty-bound, the same trust boundary as the runner itself. Validation is exact replay (rebuild and compare); `build --output` persists only under `explicit_local_export` to the consent-derived `<authorized_output_path>.transmission-ledger.json` path through the substrate's exclusive no-follow fsynced writer, and a trailing-separator authorized path is refused so the derivation can never name a hidden dotfile.

All three contracts are closed Draft 2020-12 JSON Schemas. Hashes are lowercase SHA-256 over canonical JSON (UTF-8; sorted keys; compact separators; the digest field omitted from the object being hashed). The consent receipt additionally binds a closed consentable-plan projection containing the probe id, exact claim and eligibility basis, queries and their date/index targets, provider roster, language and document-type allowlists, authorized content classes, caps, and plan creation time. Provider retention is conditional: `known` requires a semantically visible reference and `unknown` requires null. Changing any authorization surface invalidates the old receipt.

The portable schemas use `\\S` as a first structural screen. The runtime then applies one Unicode predicate to every claim/query, provider disclosure and retention reference, consent boundary, non-null provider-record id/title/author name, available abstract, successful rationale/raw output, and failure detail. It NFKC-normalizes for the check, rejects a surrogate anywhere, and rejects control/format/separator-only, combining-only, whitespace-only, and punctuation-only text. Narrative fields may use a visible letter, number, or symbol; provider-record ids and author names require a letter or number. Exact retained strings and their hashes are not rewritten by this check. A failed malformed assessment is the sole raw-output exception: whitespace-only or format-only output remains exact evidence, while its failure detail must still be semantic text.

## Live discovery adapters

`scripts/claim_standing_discovery.py` is the Track A head: one closed adapter per index (`semantic_scholar`, `openalex`, `crossref`, `arxiv`) turns a validated, consent-bound query plan into a `claim-standing-retrieval-input/1.0` record. Adapters request a single page up to the 20-hit per-(query,index) cap, truncate provider overflow at the adapter boundary with exact counts, map failures onto the closed attempt vocabulary with exactly one transport call per attempt and no silent retry, and declare honest `retention_state: unknown` provider blocks. An arXiv year filter is refused as `unsupported_query` before any network call. The emitted record carries an empty `relevance_assessments` array by design: assessments are caller-supplied under these contracts, and the relevance assessor is a later, separately consented slice, so finalization stays blocked until each computed work family has one. The `retrieve` CLI refuses to persist output under a `session_only` consent, accepts only the output path derived from the consent's hash-bound `authorized_output_path` plus a fixed `.retrieval-input.json` suffix, refuses provider redirects, and writes exclusively through the substrate's no-follow fsynced writer. The pinned resolver clients are not imported. Adapters are written against the providers' documented public APIs and are unexercised live until a first diagnostic run.

## Deterministic finalization

The pure builder `scripts/build_claim_standing_candidate_ledger.py` accepts only local JSON files. It validates consent and exact-claim bindings, then applies these operations in order:

1. require exactly one visible initial attempt for every planned query/index pair;
2. mark hits that have neither a title nor a stable identifier;
3. apply date, language, and document-type filters in that order;
4. form work families by normalized DOI, explicit version relation, normalized title/year/first author, then title plus a supplied relation; a DOI counts only after NFKC/prefix trimming when it matches `10.<4-9 ASCII digits>/<suffix>`, the suffix contains at least one Unicode letter or number, and the suffix has no Unicode C/Z/whitespace character; invalid DOI text remains retained metadata but never stable identity or a union key, normalization-empty title/provider-record id/author-family values never count as identity, and a no-DOI record cannot transitively bridge distinct DOI components;
5. choose a canonical record by published-over-preprint status, DOI presence, abstract presence, provider rank, then ASCII `(index_id, provider_record_id)`;
6. apply the caller-supplied relevance assessment independently of canonical selection, verifying its canonical exact-claim/candidate/assessor input digest and exact prompt UTF-8 digest, then retaining its outcome, raw output and matching digest, rationale, or explicit failure;
7. select relevant and ambiguous families by deterministic relevance/rank order, up to 40 families, preserve assessment failures as `not_checked`, and mark every remaining eligible family `candidate_cap_exceeded`; a derived work-family id resolves only otherwise exact ordering ties.

The envelope is fixed at three queries, four indexes, 20 retained hits in aggregate per `(query,index)` across attempts, 240 raw hits, and 40 selected work families. Every raw hit receives exactly one terminal state. Attempt failures remain separate ledger rows; the builder never hides or retries them. A pair has one initial attempt; any later attempt must name the failed attempt and a fresh, unique authorization identifier.

Relevance is an explicit retained input, not a model decision made by this builder. Each row binds the exact claim text/digest, candidate title and abstract state/text digest, assessor identity/version contract, and canonical prompt UTF-8 bytes before its output is considered. An available abstract and a successful assessment's raw output and rationale must contain visible semantic NFKC text under the rule above. A failed assessment retains a semantic failure detail and any malformed raw output exactly, including whitespace-only or format-only output, and finalizes truthfully as `not_checked`; it is never converted into a relevance judgment or omitted.

## Consent, privacy, and failure behavior

Only the exact checkpoint proposition, allowed query/index envelope, filters, retrieval content class, and retained-input hashes authorized by the consent receipt may be processed. Credential fields, API keys, full text, stance/model configuration, and network locations are outside these contracts; the only prompt field is the bounded relevance-only prompt bound to the explicit assessment input. Every planned target pair must have one visible root attempt. A retry requires a closed hash-bound authorization receipt for the exact plan, probe, consent receipt, failed attempt, and query/index pair, accepted after that failure and before the retry starts. Attempt, hit, authorization, assessment, and input timestamps are checked for their required monotonic order. A schema error, stale hash, unauthorized retry, cap violation, missing assessment, invalid Unicode, or changed exact claim fails closed without output replacement. The static integration guard separately pins every directly imported module, tracks its alias, and permits only the exact module attribute/call shapes used by the current offline runner; bare module-object escape and deeper capability paths fail the guard.

Build a new local ledger only when the hash-bound consent receipt says `local_persistence=explicit_local_export`:

```text
PYTHONPATH=scripts python scripts/build_claim_standing_candidate_ledger.py build --query-plan query_plan.json --retrieval-input retrieval_input.json --output candidate_ledger.json
```

For `local_persistence=session_only`, the same `build --output` command fails before creating the path. In-memory `build_ledger(...)` and the read-only replay validator remain available; there is no CLI flag that widens persistence authority. An authorized export requires the exact closed `export_boundary` statement and absolute `authorized_output_path` in the hash-bound receipt; the CLI requires an exact output-string match before path creation, so changing the working directory cannot retarget a receipt. It uses exclusive create plus no-follow on supported non-Windows hosts, is mode `0600` from creation even under umask `022`, and fsyncs the file and containing directory before reporting success. The ledger root copies the exact consented `local_persistence`, `export_boundary`, and authorized path, and every work family's `sharing_scope` equals that persistence state; a disk export is never mislabeled `session_only`. `rights_basis=not_assessed` remains truthful and unchanged: local persistence authority does not invent publication, redistribution, or provider rights.

Validate an existing ledger by exact deterministic replay:

```text
PYTHONPATH=scripts python scripts/build_claim_standing_candidate_ledger.py validate --query-plan query_plan.json --retrieval-input retrieval_input.json --candidate-ledger candidate_ledger.json
```

## Pipeline wiring

The probe joins the pipeline at exactly one seam: after Phase E has emitted its Claim Registry at a Stage 2.5 or Stage 4.5 integrity checkpoint, as a user-requested advisory view (`../academic-pipeline/references/claim_verification_protocol.md` § Claim-Standing Probe Offer). The wiring layer is three deterministic, offline tools; none of them retrieves, calls a model, or touches Phase E, gate, manuscript, citation, or read-ledger state (§9 gate 12, pinned by a static capability scan plus an end-to-end no-mutation test).

- `scripts/build_claim_standing_query_plan.py` (§3.1 trigger + §3.2 consent surface; gates 1 and 2). `assess_eligibility` applies the exact trigger to one registry row: at Stage 2.5 the recorded `HIGH-IMPACT` tier alone is the registry witness (`RANDOM`/`TOP-UP`/`NOT-SELECTED` never eligible) and a registry-recorded basis or a recorded researcher confirmation supplies the plan's five-part basis; Stage 4.5 requires the `ALL` registry with the recorded five-part high-impact basis (`ALL` alone is not permission), and a basis-less Stage 4.5 row stays ineligible until the researcher confirms the classification. Confirmations and the basis provenance (registry vs researcher confirmation) are recorded on the consent surface, never in the registry. `propose` renders the closed §3.2 consent surface — exact claim, providers and retention, what each recipient receives, caps, LLM transmission flags, exact stance provider/model when proposed, persistence and deletion/export boundaries with the derived artifact suffixes, the advisory/search-bounded statement, and the four separate choices — and embeds the complete consentable-plan projection of the plan `bind` would construct, so the surface SHA-256 covers every field the receipt later binds (what was shown IS what is bound; `bind` asserts the receipt's `consentable_plan_sha256` equals the digest of the projection the accepted surface displayed). `bind` then emits a schema-valid `claim-standing-query-plan/1.0` (retrieval_only) or `/1.1` (retrieval_plus_stance) plan validated by this substrate, or the explicit local `not_checked` declination record (`claim-standing-probe-declination/1.0`): `consent_absent` when no surface hash was supplied, `consent_invalidated` on any post-proposal change (claim, query, provider, filter, cap, stance plan, persistence), `consent_cancelled` on an explicit cancel — with no network or model call anywhere in the builder. Explicit falsey decisions are refused, never defaulted (an empty `queries` list does not select the default query). The default query is the `exact_claim` derivation (`exact_claim_query`); an edited text must be declared `researcher_authored`, and `assisted_then_researcher_approved` is refused because no planner mode is authorized in this slice. The `bind --output` CLI persists only under `explicit_local_export` to the consent-derived `<authorized_output_path>.query-plan.json` path; without `--output` the plan prints for session-only use and no path is created, and a declination exits with the distinct status 3 (neither a bound plan nor an error). The surface's `derived_artifact_suffixes` roster is the complete consented-artifact family (candidate ledger at the authorized path itself, query plan, retrieval input, transmission ledger, stance record, evidence rows, rendered view), sourced from the substrate's `ARTIFACT_SUFFIXES` authority and test-pinned to every owning module.
- `scripts/check_claim_standing_freshness.py` (§7; gate 13). Compares the probe identity bindings — current registry claim text, consent receipt, query plan, adapter registry, candidate ledger, stance configuration (consented provider/model and the runner's frozen prompt-contract version) — and reports `current` or `stale` with a closed reason list (`claim_text_changed`, `consent_receipt_changed`, `query_plan_changed`, `adapter_registry_changed`, `candidate_ledger_changed`, `stance_configuration_changed`) plus explicit `assessed` / `unassessed` binding lists, so a claim-text-only comparison never presents itself as a complete assessment. The record-side comparison consumes the runner's single identity authority (`expected_identity`), a stance record can only be assessed together with its candidate ledger, and artifact semantics (schema and deep replay) remain the named validators' job and are reported as unassessed here. A stale result remains inspectable but cannot be presented as current; an artifact whose self-digest does not replay is an assessment error, never a silent verdict. `--runtime-check` additionally compares the consented roster against the currently declared discovery adapters.
- `scripts/check_claim_standing_transmissions.py` (§6; gate 14). See the contract identity above.

The current slice deliberately excludes the relevance assessor, a live stance-provider adapter, measurement gates, and held-out dispatch. `STANCE CLASSIFICATION UNMEASURED` remains mandatory until a separately authorized later track is implemented and evaluated.
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