Skip to content

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

academic-paper-reviewer

Flagged

模拟同行评审:期刊匹配审稿人 + 3 位动态领域审稿人 + 魔鬼代言人,输出编辑决定(接收/小修/大修/拒稿)与返修路线图,可做方法论专项评审与再审核验。Triggers: review paper, peer review, manuscript review, check methodology, re-review | 审稿, 同行评审, 评审论文, 检查方法, 复审。只做评审,不改写稿件。

FileKindSize
SKILL.mdskill md48.9 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.0 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/devils_advocate_reviewer_agent.mdmarkdown42.6 KB
agents/domain_reviewer_agent.mdmarkdown34.0 KB
agents/editorial_synthesizer_agent.mdmarkdown42.4 KB
agents/eic_agent.mdmarkdown28.8 KB
agents/field_analyst_agent.mdmarkdown11.9 KB
agents/methodology_reviewer_agent.mdmarkdown44.6 KB
agents/perspective_reviewer_agent.mdmarkdown34.3 KB
examples/hei_paper_review_example.mdmarkdown33.8 KB
examples/interdisciplinary_review_example.mdmarkdown27.6 KB
examples/subclaim_decomposition_example.mdmarkdown8.3 KB
references/calibration_mode_protocol.mdmarkdown16.1 KB
references/changelog.mdmarkdown2.0 KB
references/editorial_decision_standards.mdmarkdown13.5 KB
references/guided_mode_protocol.mdmarkdown2.6 KB
references/integration_guide.mdmarkdown1.3 KB
references/quality_rubrics.mdmarkdown6.9 KB
references/re_review_mode_protocol.mdmarkdown52.6 KB
references/review_criteria_framework.mdmarkdown6.8 KB
references/review_panel_provenance_protocol.mdmarkdown10.1 KB
references/review_quality_thinking.mdmarkdown3.9 KB
references/reviewer_sprint_prompt_source.mdmarkdown48.5 KB
references/sprint_contract_protocol.mdmarkdown32.7 KB
references/statistical_reporting_standards.mdmarkdown30.4 KB
references/top_journals_by_field.mdmarkdown13.2 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/_text_similarity.pyscript16.0 KB
scripts/ars_cache_invalidate.pyscript1.3 KB
scripts/ars_mark_read.pyscript18.2 KB
scripts/ars_write_scope_guard.pyscript30.9 KB
scripts/arxiv_client.pyscript9.4 KB
scripts/audit_panel_claims.pyscript17.3 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

_shared/references/cross_document_consistency_advisory_protocol.md

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

This protocol defines the consumer and handoff boundary for the closed
`cross-document-consistency-advisory/1.0` family. The frozen design is
`docs/design/2026-08-10-672-cross-document-consistency-advisory-spec.md`.
The deterministic implementation is
`scripts/build_cross_document_consistency_advisory.py`.

The family consists of:

- `preregistration-artifact/1.0`, the persistent deep-research handoff sidecar;
- `cross-document-source-manifest/1.0`, the exact two-artifact source authority;
- `cross-document-consistency-advisory-draft/1.0`, untrusted semantic input;
- `cross-document-consistency-advisory/1.0`, the replay-finalized carrier; and
- `evidence-row/1.2`, whose only surface is
  `cross_document_consistency`.

## Advisory-only meaning

Every final carrier fixes `layer=LLM-ADVISORY` and
`evaluation_status=UNMEASURED`. The runtime does not call a model: it validates
caller-supplied semantic observations and exact evidence. Repository fixtures
measure contract behavior only. They do not measure semantic accuracy,
coverage, false-positive rate, or false-negative rate.

The only performed outcomes are
`POTENTIAL_INCONSISTENCY_LOCATED` and
`NO_LISTED_INCONSISTENCY_LOCATED`. The latter always means **not proof of
agreement, completeness, or a clean document**. An unperformed observation is
`check_state=not_checked` with a null outcome.

This carrier has no score, confidence, severity, PASS/FAIL, gate, readiness,
acceptance, authorization, terminal-policy effect, rewrite instruction, or
replacement text. It never creates or changes ClaimIntent, a revision roadmap,
author adjudication, patch authority, Integrity Report counts/verdicts, Phase E
claim rows, or Material Passport state. Consent/protocol review remains owned by
#667/#681; this family adds no consent/protocol role, enum, observation, or
consumer.

## Preregistration sidecar ownership

The research architect is a non-shell declarer. It records only the explicit
caller status and, for a completed supplied artifact, the explicitly named
companion handle. It must not hash the file, guess a digest, copy the repository
template into the handoff, or construct/update the sidecar itself.

Before the deep-research handoff, a shell-capable orchestrator invokes:

```bash
python scripts/build_cross_document_consistency_advisory.py \
  build-preregistration-artifact \
  --status <provided|not_provided|access_failed|retrieval_failed> \
  --declared-at <explicit-rfc3339> \
  ...
```

The named deterministic builder is the only owner allowed to create or update
`preregistration-artifact/1.0`. It emits exactly one record, including an
explicit unavailable receipt. It never reads an ambient clock. A `provided`
record binds the strict-UTF-8 companion's exact artifact/content SHA-256 and
byte sizes and uses `author_provided_completed_preregistration` provenance
(`synthetic_fixture` is reserved for repository tests). The unavailable states
have null paths and byte bindings, `not_provided` provenance, and the caller's
explicit RFC3339 declaration time.

The companion is explicitly named by the caller. The sidecar never embeds,
locates, fetches, or follows it. The repository file
`../deep-research/templates/preregistration_template.md` is guidance only and can
never be evidence or a replacement companion.

Academic-paper intake and every pipeline handoff strict-parse and replay the
same sidecar and, when provided, the same companion bytes. They then carry both
byte-for-byte without reinterpretation. Omission, silent substitution, digest
repair, or rebuilding from prose is invalid. A later explicit user supply must
produce a new fully bound sidecar through the same builder; it cannot be spliced
into the old receipt.

## Stage 4.5 source authority and replay

The source manifest contains exactly two artifacts:

1. the designated, present accepted manuscript draft; and
2. the exact projection of the current preregistration sidecar.

All manuscript and disclosure evidence roles bind the designated accepted-draft
artifact. Only the `preregistration` role binds the preregistration artifact.
Extra, unused, or prior manuscript artifacts are invalid.

Sidecar projection is exact:

| sidecar status | manifest state | binding rule |
|---|---|---|
| `provided` | `present` | same ID/path/provenance and four byte bindings |
| `not_provided` | `source_missing` | same ID; null path/bindings; `not_provided` provenance |
| `access_failed` | `access_failed` | same ID; null path/bindings; `not_provided` provenance |
| `retrieval_failed` | `retrieval_failed` | same ID; null path/bindings; `not_provided` provenance |

If a previously provided companion is unreadable or no longer replays, the
result is `SOURCE_BINDING_INVALID`. It is not downgraded to `not_checked` and no
carrier is written.

Finalization takes only explicitly named local inputs: draft, source manifest,
sidecar, accepted draft, and the preregistration companion when provided. It
strict-parses and replay-validates the complete sidecar and source bundle before
reading any observation outcome. Its `input_binding` fixes the raw draft and
manifest SHA-256, sidecar raw SHA-256 and `record_digest`, accepted-draft artifact
ID/SHA-256, and source-bundle SHA-256. Validation and rendering require those
same inputs and rebuild the carrier byte-for-byte; a self-consistent digest alone
is insufficient.

The exact `input_binding` roster is:

```text
draft_schema_version
draft_sha256
source_manifest_schema_version
source_manifest_sha256
preregistration_record_schema_version
preregistration_record_sha256
preregistration_record_digest
accepted_draft_artifact_id
accepted_draft_sha256
source_bundle_sha256
```

`source_bundle_sha256` is canonical-JSON framing over the exact manifest SHA,
sidecar raw SHA/record digest, designated accepted-draft ID/SHA, and every
manifest artifact's ID, kind, state, provenance, artifact/content hashes, and
sizes in bytewise ASCII artifact-ID order. It is never raw-byte concatenation.
`report_id` is `XDOC-` plus the first 24 lowercase hex digits of SHA-256 over
canonical compact JSON containing exactly the draft SHA, manifest SHA, sidecar
raw SHA/record digest, accepted-draft ID/SHA, and source-bundle SHA. Display
`ADV-XDOC-*` and `EVR-XDOC-*` IDs derive from canonical pair/observation-key
order; callers cannot select them.

The accepted draft limit is 8 MiB, the preregistration artifact limit is 64 MiB,
and their aggregate UTF-8 limit is 72 MiB. Files are strict UTF-8, are not
normalized, and are admitted before semantic consumption.

## Pair roster and evidence

Each carrier has exactly four pair results, in this order:

1. `abstract_results` (`abstract`, `results`);
2. `discussion_results` (`discussion`, `results`);
3. `methods_reported_analyses` (`methods`, `reported_analyses`); and
4. `manuscript_preregistration` (`manuscript_report`, `preregistration`,
   `disclosure_scope`).

The performed finding vocabulary is closed:

| pair | allowed finding types |
|---|---|
| `abstract_results` | `numeric_mismatch`, `direction_mismatch`, `significance_mismatch`, `claim_strength_rung_mismatch` |
| `discussion_results` | `direction_mismatch`, `claim_strength_rung_mismatch`, `scope_or_population_overreach` |
| `methods_reported_analyses` | `declared_analysis_no_reported_counterpart`, `reported_analysis_no_declared_counterpart`, `analysis_specification_conflict` |
| `manuscript_preregistration` | `undisclosed_preregistration_deviation` |

The first three use exactly two evidence slots. The preregistration pair uses
exactly three; its manuscript disclosure witness is never optional for a
performed observation. Logical roles remain distinct even when several roles
bind the same accepted manuscript bytes.

Methods absence requires one quote and one `checked_no_match` over an exact,
non-empty, explicitly named counterpart scope. A generic, incomplete, blank, or
unprovided scope is `not_checked`, never evidence of absence. An undisclosed
preregistration-deviation observation requires manuscript and preregistration
quotes plus `checked_no_match` over the exact named manuscript disclosure scope.
An exact disclosure quote for the same `deviation_id` produces a no-listed
observation; absent or unreplayed disclosure scope makes the whole observation
not checked.

Performed no-listed observations use only `legitimate_compression`,
`same_rung_rewording`, `disclosed_deviation`, or
`other_no_listed_observation`, under their pair-specific schema branches. A
checked scope carries
`caller_declared_complete_named_scope_not_independently_authenticated`; this is
replay provenance, not independent proof of completeness. Not-checked reasons
are closed to `PAIR_CHECK_NOT_PERFORMED`, `COUNTERPART_DOCUMENT_MISSING`,
`COUNTERPART_SCOPE_NOT_PROVIDED`, `SOURCE_ACCESS_FAILED`, and
`SOURCE_RETRIEVAL_FAILED`. Missing source takes precedence, then access failure,
then retrieval failure. Invalid schema, role, digest, or replay is a contract
error and cannot be laundered into one of those receipts.

`evidence-row/1.2` is separate from 1.0 and 1.1. It carries the complete ordered
bilateral or trilateral evidence unit under
`surface=cross_document_consistency`. The legacy 1.0 Phase E shape and 1.1
authority-profile content-coverage shape, their schemas, runtime behavior, and
serialized identities remain unchanged. Versions/surfaces cannot be mixed.

Every positive quote or checked scope is exact-source bound. External text is
strictly percent-decoded once (`+` stays literal), capped at 25 Python
whitespace-split words and 1,000 Unicode code points, hashed, and replayed by a
half-open UTF-8 byte span. Overflow is rejected rather than truncated. All text
is rendered inert and defaults to `session_only/not_assessed`; shareable rows
require the paired user-declared rights value. No cache, network, retrieval,
normalization, or ambient clock participates.

The field-relative ladder in
`_shared/references/claim_strength_ladder.md` is semantic caller guidance only.
There is no deterministic keyword matcher or numeric ranker, and no ladder
observation grants revision authority.

## Legacy multi-file audit non-migration

The existing Codex multi-file audit runner, its rounds/convergence state, and
its `audit_artifact_entry` gate remain separate legacy consumers. An old
multi-file audit `PASS` cannot be mapped, projected, or translated into
`NO_LISTED_INCONSISTENCY_LOCATED`. Conversely, a #672
`POTENTIAL_INCONSISTENCY_LOCATED` observation cannot be mapped, projected, or
translated into an old-audit P1/P2/P3 finding, `PASS` / `MINOR` / `MATERIAL`
verdict, gate result, convergence decision, or `audit_artifact_entry`.

#672 never invokes the legacy runner, consumes an old audit output, or writes
into its carrier. Existing audit behavior and bytes remain unchanged; the two
surfaces may be shown independently but cannot satisfy, suppress, aggregate, or
change one another.

## Pipeline coexistence with #660

#660 tortured-phrase screening and #672 run inside the **single existing**
mandatory Stage-5 entry checkpoint after the same exact Stage 4.5 PASS. The
orchestrator runs #660 first and #672 second and surfaces two independent
carriers. The exact machine join is:

```text
#660 input_binding.artifact.artifact_id
  == #672 input_binding.accepted_draft_artifact_id
#660 input_binding.artifact.artifact_sha256
  == #672 input_binding.accepted_draft_sha256
```

Neither carrier consumes, suppresses, aggregates, or changes the other. A #660
loaded-snapshot failure may still write its schema-valid degraded artifact and
exit 1; the checkpoint preserves and validates it. A #672 contract/runtime
failure writes no output and records only a bounded, redacted
`ADVISORY_UNAVAILABLE:<CODE>` diagnostic. Neither behavior changes Stage 4.5,
blocks or delays the mandatory checkpoint, requires remediation, or alters
Stage-5 dispatch after user confirmation.

Any manuscript revision makes both carriers stale. The manuscript must re-enter
integrity review, obtain a new exact Stage 4.5 PASS, and rerun #660 then #672
against the same new accepted bytes. Reusing either carrier or rerunning only one
is invalid cargo.

This advisory is not a formatter input, Phase E row, Material Passport terminal
state, or additional checkpoint. It is displayed as a separate `ADV-XDOC-*`
table at the existing checkpoint.

## Rendering, failure, and measurement limits

`render` performs the same full replay before display. One explicit page contains
at most 25 observations; `--all` does not exist. Navigation names the preceding
or next explicit page, while the complete canonical JSON remains authoritative.

On #672 failure, no schema-valid output is created or replaced. Only a closed
`ADVISORY_UNAVAILABLE:<CODE>` diagnostic of at most 80 ASCII characters is
retained; it cannot contain source/quote text, local paths, or raw exceptions.
The diagnostic is informational and nonblocking.

Held-out documentation remains `UNMEASURED`. No measurement JSON, model output,
judge record, live model/API call, expensive evaluation, semantic efficacy claim,
or clean-document claim is authorized by this protocol.
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