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/evidence_row_protocol.md

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

This protocol is the runtime-facing authority for evidence rows. The canonical
field shape is `_shared/contracts/evidence/evidence_row.schema.json`; cross-field
semantics are implemented by `scripts/evidence_rows.py`; the frozen decision is
`docs/design/2026-08-09-656-shared-evidence-row-contract-spec.md`.

## V1 surface and persistence

V1 has one live surface:

```text
surface = phase_e_claim_verification
Integrity Report.phases.E_claims.evidence_rows[]
```

The Integrity Verification Agent emits one row per selected
`(claim_id, ref_slug, anchor)` tuple. The full ordered array travels inside the
existing Schema 5 Integrity Report. It is not a new passport aggregate. A
multi-citation claim keeps one row per citation; `E_claims.checked` and verdict
summaries continue to count distinct claims.

The Stage 4 -> 5 opt-in `claim_audit_results[]` contract is a different lifecycle
and is not a V1 producer or consumer.

## Producer sequence

For each selected tuple:

1. Pass the candidate row and, when available, its exact session-held source text
   directly to `build`. Never pass a URL for the builder to fetch.
2. Preserve the v3.7.3 anchor's encoded value. The builder validates and decodes
   it exactly once with strict UTF-8.
3. For a `page` or `section` anchor, pass only the bounded passage the agent
   actually relied on. The builder requires that passage to be an exact substring
   of the held source text. It does not authenticate the locator.
4. Pass an explicit failure state when an upstream access or extraction attempt
   failed. Never copy the claim, writer anchor, error message, or placeholder into
   `excerpt.text`.
5. Persist the returned row unchanged. Render only the persisted row array.

The builder, not producer prose, decides the evidence state:

| Anchor / input | State | Excerpt |
|---|---|---|
| `quote`, exact once-decoded source match | `verified_exact_match` | exact matched text |
| `quote`, held source mismatch | `unconfirmed_anchor` | null |
| `page` / `section`, supplied passage exactly in held source | `agent_extracted` | exact passage |
| `paragraph` | `not_checked` | null |
| any non-`none` anchor, no held source | `source_missing` | null |
| explicit stable permission/paywall failure | `access_failed` | null |
| explicit upstream retrieval/extraction failure | `retrieval_failed` | null |
| explicit unperformed check | `not_checked` | null |
| `none` / absent marker normalized to `none` | `anchorless` | null |

The canonical display labels come only from `scripts/evidence_rows.py`. “Verified”
in `VERIFIED EXACT MATCH` applies to excerpt provenance, not the Phase E claim
verdict.

## Exactness and budgets

- Source-content SHA-256 covers the exact held source string encoded as UTF-8.
  Artifact/PDF hashes are separate nullable provenance and cannot substitute.
- No Unicode, case, whitespace, newline, or punctuation normalization occurs.
- Percent decoding runs once. `%HH` must be well formed and yield strict UTF-8;
  `+` remains a plus sign.
- Quote anchors and excerpts are at most 25 whitespace-split words and 1,000
  Unicode code points. Over-budget rows fail; they are not truncated.
- Positive excerpts carry a SHA-256 plus a half-open UTF-8 byte span. Replaying
  that span against the exact source content must yield the excerpt bytes.
- `row_sha256` binds the canonical complete row except for the digest field itself.

## Cache replay

Only `verified_exact_match`, `agent_extracted`, and `unconfirmed_anchor` are
cacheable. A candidate hit is revalidated against the current explicit source,
anchor, schema, hashes, budgets, and state transition. Source or anchor drift is a
miss. A corrupt cache candidate fails closed as a cache input: the builder
discards it and rebuilds from the current explicit source/anchor inputs, and
corrupt content is never returned or displayed as a hit.

A hit preserves the evidence state, excerpt bytes, byte span, and capture time.
It changes the cache status to `hit` and recomputes the row digest. Empty/failure
states use `not_used`. Renderers never read or write cache entries.

## Checkpoint rendering

`render_markdown` and `render_html` require an explicit in-memory
`ref_slug -> exact session-held source text` map for every source-bound row.
The CLI builds that map from a `--source-map` JSON file or, for V1 rows, from `--source-dir`,
a folder holding one file per source, named by `source_file_name(ref_slug)`, of
which it reads only the files the source-bound rows name, as exact UTF-8 bytes
(#933). The Phase E integrity agent writes that folder so a checkpoint in
another session can replay its rows.
Before display they replay `verified_exact_match`, `agent_extracted`, and
`unconfirmed_anchor` against that text. Missing replay text is a render failure:
a self-consistent row plus unkeyed digests cannot prove where writer-controlled
text came from.

The renderers do not retrieve or open a source, corpus item, sibling path, URL,
DOI, cache, environment variable, or model tool. Replay validation recomputes
the strict once-decode and source-bound hashes, but never decodes the stored
display value again, extracts new text, derives a new state, or mutates the row.

Markdown and HTML surfaces use the same fixed evidence labels and treat every
claim, locator, source label, detail, decoded anchor, and excerpt as untrusted
data. A payload cannot create a tag, comment, link, image, heading, fence, extra
table cell/row, or prompt instruction. Only bounded stored evidence appears;
surrounding source context never does.

The default and maximum page size are 25 rows; a caller may request a smaller
positive page. Each page reports its one-based page, total pages, row interval,
and total rows. There is no render-all mode and no total-row cap. Walking the
pages preserves every row exactly once in document order.

## Rights and privacy

Rows default to:

```json
{
  "sharing_scope": "session_only",
  "rights_basis": "not_assessed"
}
```

A user-confirmed shareable row must pair with
`rights_basis=user_declared_authorized`. The contract never infers permission from
source location or availability. A 25-word excerpt is an adjudication aid, not a
license finding. Exporters that cannot preserve the caveat remove the excerpt.

No full text, abstract, private notes, surrounding context, API credential, or
rendered markup belongs in an evidence row.

## Legacy and degradation

A positively identified pre-#656 Schema 5 report may omit `evidence_rows`; use
the explicit `--allow-legacy-absence` compatibility flag to render it as
`LEGACY — EVIDENCE ROWS UNAVAILABLE`. Missing shape alone is not legacy proof,
and render fails without the flag. Do not interpret absence as an empty
successful check and do not synthesize historical excerpts. A current producer
with selected tuples must emit corresponding rows, including explicit empty
states, and may never use the compatibility flag.

For a current report, distinct row `claim_id` count must equal
`E_claims.checked`, distinct claims with Phase E verdict `VERIFIED` must equal
`E_claims.verified`, and rows sharing one `claim_id` must repeat the same claim
object and verdict. These checks reject an empty-success carrier and
contradictory multi-source rows. Exact tuple coverage is still audited against
the E1 Claim Registry, which remains the selection authority and is not copied
into a second V1 machine manifest.

Failure states do not alter Phase E verdict taxonomy or gate logic. The evidence
row is an adjudication view, not a new closure condition.

## Human-read boundary

Seeing an excerpt at a checkpoint is not reading the source. Evidence-row build,
validation, cache replay, and rendering never call `/ars-mark-read`, never write a
human-read log, and never change `human_read_source`, `read_scope`, latest-event
resolution, or LOW-WARN promotion.

## Consumer rule

Consumers reference this protocol and the schema by pointer. They consume the
machine row, not a copied enum or a parsed rendered table. They may not upgrade
`unconfirmed_anchor`, `not_checked`, `source_missing`, `access_failed`,
`retrieval_failed`, or `anchorless` into evidence-bearing states.

## Version 1.1 (`evidence-row/1.1`) authority-profile advisory extension (#681)

`_shared/contracts/evidence/evidence_row_v1_1.schema.json` is a separate closed
version for `surface=authority_profile_content_coverage`. It does not extend the
Phase E row in place: `claim`, `verdict`, and `detail` are absent, and exact
`requirement_pointer`, `authority_anchor_pointer`,
`structured_expectations[]` pointer/digest, packet artifact, and advisory
document-locator bindings replace them. Version 1.0 producer behavior, cache
semantics, persisted bytes, and Phase E rendering remain unchanged. A page may
contain only one evidence-row version/surface.

The 1.1 builder is `build_advisory(...)`. It records only passage provenance;
it never chooses an `advisory_coverage_status`, interprets a structured
expectation, opens a packet path, retrieves content, or calls a model/API. The
closed states are:

- `agent_extracted`: a once-decoded, bounded quote is an exact substring of the
  explicitly supplied artifact string;
- `checked_no_match`: the explicit artifact string was checked, with no quote
  or excerpt persisted; and
- `not_checked`, `source_missing`, `access_failed`, and `retrieval_failed`:
  explicit unperformed/empty states with null content binding and excerpt.

Both source-bound states require replay from an explicit
`artifact_id -> exact session-held content` map before rendering. V1.1 retains
the same strict once-decode, 25-word/1,000-code-point bounds, exact UTF-8 content
hash and byte-span rules, inert Markdown/HTML treatment, rights pairing, and
human-read-ledger noninterference. It deliberately fixes `cache.status` to
`not_used` and `cache.key_sha256` to null.
For a positive row, `captured_at` is the explicit RFC 3339 timestamp carried by
the closed advisory draft; it is not invented from the authority-context
confirmation time or the runtime clock.

V1.1 rows are nested only in the replay-bound
`content-coverage-advisory/1.0` carrier defined by
`_shared/contracts/human_subjects/content_coverage_advisory.schema.json` and
`_shared/references/authority_content_coverage_advisory_protocol.md`. Their
labels remain `LLM-ADVISORY`; neither an exact passage nor a checked-no-match
state changes #667 deterministic status, readiness, authorization, or
institutional acceptance, and neither is an adequacy or efficacy finding.

## Version 1.2 cross-document consistency extension (#672)

`_shared/contracts/evidence/evidence_row_v1_2.schema.json` is a separate closed
version whose only surface is `cross_document_consistency`. It is nested only in
`cross-document-consistency-advisory/1.0` and is finalized and replayed by
`scripts/build_cross_document_consistency_advisory.py`. It does not widen either
earlier schema or enter the Phase E Integrity Report. The 1.0 and 1.1 schemas,
`scripts/evidence_rows.py` behavior, cache semantics, rendering, and serialized
identities remain unchanged; versions and surfaces cannot be mixed.

One 1.2 row is the complete ordered evidence unit for one observation. The first
three pair kinds have two logical-role slots. Manuscript/preregistration has
exactly three: `manuscript_report`, `preregistration`, then the manuscript-bound
`disclosure_scope`. Logical roles remain distinct even when several bind the
same accepted manuscript bytes.

Its states are `agent_extracted`, `checked_no_match`, `not_checked`,
`source_missing`, `access_failed`, and `retrieval_failed`. A quote is exact-span
replayed. `checked_no_match` binds an exact, non-empty, named source scope and
only records the caller's semantic assertion that no counterpart was located;
it does not prove semantic absence or scope completeness. Methods absence
requires one quote plus a checked counterpart scope. An undisclosed
preregistration deviation requires two quotes plus its third checked disclosure
scope. Consumers cannot promote an unavailable or unperformed slot.

V1.2 retains strict single percent decode with literal `+`, the 25-word and
1,000-code-point ceilings, exact strict-UTF-8 hash/span replay, inert rendering,
and paired sharing/rights values. It performs no cache lookup, model/API call,
retrieval, normalization, or ambient-clock read. One canonical `row_sha256`
binds the complete bilateral or trilateral row.

The row supports only a caller-supplied `LLM-ADVISORY` / `UNMEASURED`
observation. It creates no PASS/FAIL, score, gate, clean/agreement certificate,
ClaimIntent, revision authority, or consent/protocol finding. See
`_shared/references/cross_document_consistency_advisory_protocol.md`.

## Version 1.3 claim-standing advisory surface (#655)

`_shared/contracts/evidence/evidence_row_v1_3.schema.json` defines
`evidence-row/1.3`, surface `claim_standing_advisory`: one provenance-only row
per (probe claim, selected work-family candidate) in the #655 claim-standing
probe. The row binds a bounded inspected-evidence excerpt to the exact source
content hash and UTF-8 span, reuses the family's cache, content-handling, and
row-hash blocks verbatim, and carries a `coverage` declaration
(`abstract` / `session_held_full_text` / `metadata_only`) in place of 1.0's
anchor: the two anchor-derived excerpt states do not exist on this surface.
Cross-field conditionals bind retrieved states to a full payload and a bound
source, non-retrieved states to null payloads and `contains_external_text:
false`, the rights coupling in both directions, and metadata-only coverage to
failure states with a null source hash. The row never carries a stance or
verdict; an exact excerpt match never determines stance; abstract-level
coverage is never rendered as verified full text. The consuming stance record
(`claim-standing-stance-record/1.0`) references rows by id AND row hash. No
runtime validator for this surface exists yet — the future stance runner owns
replay verification before rendering.
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