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

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

This protocol governs exact authority selection and deterministic applicability
tracing. It is not a committee, legal opinion, authorization, compliance result,
submission-readiness result, or review-pathway result.

Canonical artifacts:

- `_shared/contracts/human_subjects/irb_context_record.schema.json`
- `_shared/contracts/human_subjects/authority_profile_registry.schema.json`
- `_shared/contracts/human_subjects/resolved_authority_context.schema.json`
- `_shared/human_subjects_authority_registry.json`
- `scripts/resolve_human_subjects_authority.py`
- `docs/design/2026-08-09-666-human-subjects-authority-contract-spec.md`

The schemas are authoritative for field names and local shape. This protocol
governs cross-artifact use.

## Two axes and bounded profiles

V1 has exactly two axes: `review_ethics` and `data_protection`. A study may select
multiple profiles on either axis. Funder and institutional requirements are
overlays, never axes.

Every shipped profile carries `coverage_status=bounded_subset` and
`no_completeness_claim=true`:

- `us.hhs.45-cfr-46.subpart-a`
- `tw.mohw.human-subjects-research-act`
- `eu.gdpr.research-core-bounded`

Profiles contain curator summaries and primary-source links, not a claim of
complete law or legal advice. Do not vendor unlicensed normative text.

## Author declaration

The context record uses:

- `context_record_id`
- `confirmed_by=author`
- `confirmed_at`
- `applicability_as_of`
- `scope_dimensions`
- typed `declared_facts`
- `profile_selection_state` and exact `selected_profiles`
- `overlay_selection_state` and exact `selected_overlays`
- `display_precedence`

Do not infer any of these from locale, language, affiliation, filenames,
manuscript text, or model memory.

Each selected profile pins axis, id, version, digest, and authority scope ids.
Each selected overlay pins kind, axis, id, version, and digest. Unknown or
mismatched pointers fail; never choose a latest version automatically.

An empty scope-dimension list is unknown, not confirmed absence. A missing fact or
a fact with `state=unknown` and `value=null` is `unknown`, never false.
`overlay_selection_state=not_provided` is distinct from
`none_declared_by_author`.

## Predicate evaluation

Registry predicates are a closed recursive AST with only:

- `fact_equals`
- `fact_in`
- `fact_contains`
- `all`
- `any`
- `not`

Facts must resolve through `fact_definitions`, and declared value types must agree
with the catalogue. Do not execute string expressions or add profile-specific
branches.

`fact_equals` and `fact_in` accept scalar boolean, string, string-enum, or date
facts only, and every date operand must be a real ISO 8601 calendar date.
`fact_contains` means exact membership in a `string_set`; it never performs
substring matching on a string. V1 has no string-set equality operator.

Use Strong Kleene logic:

- missing or unknown fact leaf → `unknown`;
- `all`: false if any false, true if all true, otherwise unknown;
- `any`: true if any true, false if all false, otherwise unknown;
- `not(true)=false`, `not(false)=true`, `not(unknown)=unknown`.

A selected profile whose predicate is false emits `PROFILE_SCOPE_CONFLICT`; an
unknown predicate emits `APPLICABILITY_UNRESOLVED`. Both block the downstream
gate, and the resolver does not assert legal non-applicability.
Requirement predicate results remain `true | false | unknown` and never become a
compliance conclusion.

## Authority provenance

Source records separately record `canonical_url`, `snapshot_url`,
`provision_locator`, closed `allowed_provisions`, `effective_from`, `effective_until`,
`source_amended_or_published_date`, `retrieved_at`, `verified_at`,
`source_language`, `controlling_language`, `authenticity_status`,
`content_digest`, `digest_scope`, `rights_status`, and `freshness`. Row-local
`authority_anchor` records use their schema-defined counterparts, including
`authority_url`, `provision`, and `effective_date`.

The anchor source must occur in its profile or overlay `source_ids`; its
`provision` must occur in that source's `allowed_provisions`; and its
`effective_date` must equal the source's provision-specific `effective_from`.

Never infer an effective date from an amendment date. For Taiwan, the page's
amendment date belongs in `source_amended_or_published_date`; it is not, without a
separate controlling-authority basis, the profile's `effective_from` or a
requirement's `effective_date`. Keep the controlling Chinese source distinct from
the official English reference translation.

Future-effective, expired, stale, unverified, superseded, or
non-controlling-translation-only authority produces
`AUTHORITY_SOURCE_NOT_CURRENT`. Runtime resolution is offline; it never refreshes
these records from the network.

## Requirements and overlays

Every requirement identifies its axis, obligated actor, consumer scopes,
applicability AST, structured expectations, expected evidence and holder,
waiver/exception route, authoritative decision maker, collision metadata, and
full authority anchor.

Consumers must respect `obligated_actor` and `consumer_scopes`. Committee
composition evidence held by an IRB is not an investigator packet requirement.
A profiled exception route records only that a route exists; it never means the
route was applicable, requested, or granted.

Overlays use exact `target_profiles` id/version/digest pointers. Their operation is
`add`, `supplement`, or `conflict`, and `requirements_removed` is always false.
They cannot replace a base profile, delete a base row, fill an unresolved axis, or
introduce a funder axis.

Every target profile must be selected exactly. An overlay inherits the Strong
Kleene `all` of all target-profile applicability results; each overlay requirement
combines that inherited result with its own predicate using Strong Kleene `all`.
If any target is false or unknown, emit `OVERLAY_BASE_UNRESOLVED`, preserve that
tri-state result on the overlay requirements, and keep the downstream gate closed.

## Display-only precedence and collisions

`display_precedence` and resolved `trace_order` are presentation order only.
Every precedence entry says `display_only_no_suppression`.

Changing display order must not change selected authorities, predicate results,
unresolved reasons, downstream gates, collision membership, or requirement
accounting. Every requirement result appears exactly once in `trace_order`.

Requirements sharing a collision key remain parallel with
`parallel_authorities_require_human_resolution` and
`requirements_removed=false`. Never average or deduplicate different
jurisdictions or the two independent axes.

## Resolver procedure

1. Read only the explicitly supplied context and registry JSON files.
2. Reject duplicate JSON keys, non-finite values, and unknown fields.
3. Validate the context and registry schemas.
4. Recompute and match every selected profile/overlay id, version, and digest.
5. Resolve authority scopes and exact overlay targets without fallback.
6. Require selected base profiles on both axes.
7. Validate source interval, freshness, language, authenticity, digest, and rights
   metadata at `applicability_as_of`.
8. Evaluate every profile and requirement AST using Strong Kleene logic.
9. Account for every selected requirement exactly once.
10. Preserve all collisions and build display-only `trace_order`.
11. Emit the pointer-only resolved artifact and canonical digests; compute
    `resolved_digest` with its own field excluded.

The resolver does not read manuscripts, scan sibling files, access the network,
judge prose, decide legal applicability, or render a user-facing brief.

## Pointer-only result and gate

The resolved artifact carries a `context_pointer` and `registry_pointer`; it does
not embed either input. Profile, overlay, requirement, and authority-anchor data
are represented through schema-defined pointers and digests.

Its states are `resolved`, `jurisdiction_unresolved`, and
`applicability_unresolved`. Its closed unresolved codes are:

- `JURISDICTION_UNRESOLVED`
- `APPLICABILITY_UNRESOLVED`
- `OVERLAY_BASE_UNRESOLVED`
- `AUTHORITY_SOURCE_NOT_CURRENT`
- `PROFILE_SCOPE_CONFLICT`

Each unresolved reason contains exactly `code`, `axis`, nullable `authority_id`,
and nullable `requirement_id`. It contains no prose or free-text detail. A
requirement-level reason identifies its requirement; profile-, overlay-, and
missing-axis reasons use `requirement_id=null`.

The downstream gate contains exactly:

```json
{
  "both_axes_selected": true,
  "exact_selection_resolved": true,
  "all_applicability_resolved": true,
  "profile_dependent_result_allowed": true
}
```

Only `resolution_state=resolved` may set all four true. A resolved result contains
at least one selected profile on each axis, every selected profile has
`applicability=true` and `source_state=current`, and no requirement applicability
is unknown. Either unresolved state requires an unresolved reason and forces
`profile_dependent_result_allowed=false`. A profile or overlay on one axis never
cures a missing base profile on the other.

Before consuming a serialized result, call
`validate_resolved_context(result, context, registry)`. It validates the bound
inputs, deterministically replays resolution, recomputes `resolved_digest` with
that field excluded, and requires exact object equality. The replay checker—not
JSON Schema alone—owns semantic uniqueness across rows, JSON Pointer resolution,
digest-to-input binding, and gate derivation.

## Consumer boundary

- #667 consumes a serialized authority result only after
  `validate_resolved_context(result, context, registry)` succeeds and the
  profile-dependent gate is open. It filters to `submission_packet`, preserves
  exact requirement and authority-anchor pointers, and then uses only the
  closed `evidence_expected` fields `evidence_id`, `held_by`, and
  `artifact_type` for status derivation. It never interprets, evaluates, or copies
  `structured_expectations` or an evidence description; exact whole-row bytes are
  canonical-hashed only for replay integrity. Content-coverage questions belong
  to #681.
- #681 consumes authority rows only through a #667 manifest that has first been
  replay-validated against this same context/registry/resolved triplet and its
  exact packet inventory/root. It may then dereference exact
  `structured_expectations[]` pointers and join separately session-held content
  through `_shared/references/authority_content_coverage_advisory_protocol.md`.
  Its carrier is always `LLM-ADVISORY` and `UNMEASURED`; it cannot alter
  applicability, deterministic packet status, readiness, caller authorization,
  institutional acceptance, or any authority pointer/digest.
- #668 remains valid in `artifact_agnostic` mode and no profile may rewrite its
  source correspondence or committee authority.
- #669 consumes every selected-profile requirement scoped to `pathway_trace`
  only after exact #666 replay, then projects exact fact occurrences,
  authoritative-decision-maker role ids, and authority anchors under
  `_shared/references/review_pathway_rule_trace_protocol.md`. Its caller-owned
  candidate names and ordering are display-only; the trace never determines,
  predicts, ranks, approves, clears, exempts, authorizes, or gates. A missing
  profile preserves `JURISDICTION_UNRESOLVED`. The protocol's narrow display of
  requirement-level unknown predicates does not open or alter this resolver's
  `profile_dependent_result_allowed` gate.
- #680 owns correction and migration of mixed-jurisdiction reference prose.

#666 itself changes no user-facing output. It emits no verdict, pathway,
readiness, authorization, conformance result, or timeline. The #665 independent
status grammar and fixed non-authorization footer remain unchanged.

## #667 capability-envelope facts

The registry also catalogs seven author-declared booleans used only to decide
whether the deterministic submission-packet checker is within its V1 technical
capability envelope:

- `packet_v1.non_clinical=true`
- `packet_v1.single_institution=true`
- `packet_v1.competent_adults_only=true`
- `packet_v1.biospecimens_involved=false`
- `packet_v1.regulated_clinical_trial=false`
- `packet_v1.cross_border_material_transfer=false`
- `packet_v1.multisite_reliance=false`

These facts are not legal characterizations and cannot select an authority,
satisfy an axis, or change a profile or requirement digest. A missing, unknown,
or non-matching value makes #667 return `APPLICABILITY_UNRESOLVED`; it never
means that an authority is legally inapplicable. The complete #667 contract is
`_shared/references/submission_packet_manifest_protocol.md`.
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