Update Review Pack V0.3 white paper canonical draft

DEVELOPMENT_LEDGER.jsonl

@@ -27,3 +27,4 @@
 {"date":"2026-05-04","change_id":"p47-review-pack-v0.3-technical-note-v3","area":"docs","summary":"Added a docs-only v3 technical note for Review Pack V0.3.","agent_facing_impact":"Agents and reviewers get a tighter technical note with selected abstract, stable four-part contribution framing, compact diagrams, an evaluation evidence table, and preserved non-claims.","verification":"pytest -q, capabilities JSON parsing, metadata generation --check, ledger JSONL parse, boundary grep, git diff --check, and ruff.","evidence_integrity_impact":"Refines the writing artifact without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external submission, or AI Act Pack implementation.","next_action":"Review v3 before deciding whether to prepare a repository white paper or Zenodo technical report package."}
 {"date":"2026-05-04","change_id":"p49-review-pack-v0.3-white-paper-index","area":"docs","summary":"Added a docs-only white paper index for Review Pack V0.3.","agent_facing_impact":"Agents and reviewers get a canonical reading entrypoint that identifies technical note v3, supporting materials, target readers, external-sharing checklist, DOI note, and claims boundaries.","verification":"pytest -q, capabilities JSON parsing, metadata generation --check, ledger JSONL parse, boundary grep, git diff --check, and ruff.","evidence_integrity_impact":"Organizes existing white paper material without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation.","next_action":"Plan white paper polish before any Zenodo technical report, arXiv, workshop, or AI Act Pack decision."}
 {"date":"2026-05-04","change_id":"p51-review-pack-v0.3-technical-note-v3.1","area":"docs","summary":"Added a docs-only v3.1 technical note polish for Review Pack V0.3.","agent_facing_impact":"Agents and reviewers get refined abstract wording, consistent terminology, polished figure labels, stable contribution framing, retained evaluation evidence, and preserved non-claims.","verification":"pytest -q, capabilities JSON parsing, metadata generation --check, ledger JSONL parse, boundary grep, git diff --check, and ruff.","evidence_integrity_impact":"Polishes the writing artifact without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation.","next_action":"Review v3.1 before deciding whether to update the white paper index canonical draft."}
+{"date":"2026-05-04","change_id":"p53-white-paper-index-canonical-v3-1","area":"docs","summary":"Updated the Review Pack V0.3 white paper index canonical draft from v3 to v3.1.","agent_facing_impact":"Agents and reviewers now start from the polished v3.1 technical note while keeping v3, v2, and the submission plan as supporting background.","verification":"pytest -q, capabilities JSON parsing, metadata generation --check, ledger JSONL parse, index sanity check, boundary grep, git diff --check, and ruff.","evidence_integrity_impact":"Updates white paper navigation without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation.","next_action":"Run post-merge index sanity before deciding on Chinese summary or Zenodo technical report planning."}

DEVELOPMENT_LEDGER.md

@@ -57,3 +57,4 @@ generated agent metadata surfaces.
 | 2026-05-04 | p47-review-pack-v0.3-technical-note-v3 | docs | Added a docs-only v3 technical note for Review Pack V0.3. | Agents and reviewers get a tighter technical note with selected abstract, stable four-part contribution framing, compact diagrams, an evaluation evidence table, and preserved non-claims. | `pytest -q`, capabilities JSON parsing, metadata generation `--check`, ledger JSONL parse, boundary grep, `git diff --check`, and ruff. | Refines the writing artifact without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external submission, or AI Act Pack implementation. | Review v3 before deciding whether to prepare a repository white paper or Zenodo technical report package. |
 | 2026-05-04 | p49-review-pack-v0.3-white-paper-index | docs | Added a docs-only white paper index for Review Pack V0.3. | Agents and reviewers get a canonical reading entrypoint that identifies technical note v3, supporting materials, target readers, external-sharing checklist, DOI note, and claims boundaries. | `pytest -q`, capabilities JSON parsing, metadata generation `--check`, ledger JSONL parse, boundary grep, `git diff --check`, and ruff. | Organizes existing white paper material without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation. | Plan white paper polish before any Zenodo technical report, arXiv, workshop, or AI Act Pack decision. |
 | 2026-05-04 | p51-review-pack-v0.3-technical-note-v3.1 | docs | Added a docs-only v3.1 technical note polish for Review Pack V0.3. | Agents and reviewers get refined abstract wording, consistent terminology, polished figure labels, stable contribution framing, retained evaluation evidence, and preserved non-claims. | `pytest -q`, capabilities JSON parsing, metadata generation `--check`, ledger JSONL parse, boundary grep, `git diff --check`, and ruff. | Polishes the writing artifact without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation. | Review v3.1 before deciding whether to update the white paper index canonical draft. |
+| 2026-05-04 | p53-white-paper-index-canonical-v3-1 | docs | Updated the Review Pack V0.3 white paper index canonical draft from v3 to v3.1. | Agents and reviewers now start from the polished v3.1 technical note while keeping v3, v2, and the submission plan as supporting background. | `pytest -q`, capabilities JSON parsing, metadata generation `--check`, ledger JSONL parse, index sanity check, boundary grep, `git diff --check`, and ruff. | Updates white paper navigation without code changes, release changes, OpenAPI/MCP changes, schema/core changes, external publication, or AI Act Pack implementation. | Run post-merge index sanity before deciding on Chinese summary or Zenodo technical report planning. |

docs/research/review-pack-v0.3-white-paper-index.md

@@ -13,28 +13,30 @@ Pack. It does not add implementation scope or publication claims.
 
 Canonical draft:
 
-- [Review Pack V0.3 Technical Note V3](review-pack-v0.3-technical-note-v3.md)
+- [Review Pack V0.3 Technical Note V3.1](review-pack-v0.3-technical-note-v3.1.md)
 
 Supporting background:
 
+- [Review Pack V0.3 Technical Note V3](review-pack-v0.3-technical-note-v3.md)
 - [Review Pack V0.3 Technical Note V2](review-pack-v0.3-technical-note-v2.md)
 - [Review Pack V0.3 Submission Plan](review-pack-v0.3-submission-plan.md)
 - [Operation Accountability Profile](operation-accountability-profile.md)
 - [FDO / Data-Space Mapping](fdo-data-space-mapping.md)
 - [Strategic Positioning](../strategic-positioning.md)
 - [Review Pack Minimal Cookbook](../cookbooks/review_pack_minimal.md)
 
-The current recommendation is to treat V3 as the canonical repository white
-paper draft. No immediate V3.1 is required. A Zenodo technical report should
-wait until one more refinement cycle. arXiv and workshop submission remain
-deferred.
+The current recommendation is to treat V3.1 as the canonical repository white
+paper draft. V3 remains a previous draft and supporting background. V2 remains
+supporting background. The submission plan remains planning background. A
+Zenodo technical report should wait until one more refinement cycle. arXiv and
+workshop submission remain deferred.
 
 ## Reading Order
 
 1. [Strategic Positioning](../strategic-positioning.md)
    - Start here to understand the project boundary after v0.6.0: local
      evidence export, validation, verification, and review packaging.
-2. [Review Pack V0.3 Technical Note V3](review-pack-v0.3-technical-note-v3.md)
+2. [Review Pack V0.3 Technical Note V3.1](review-pack-v0.3-technical-note-v3.1.md)
    - Read this as the canonical technical note draft and repository white
      paper seed.
 3. [Review Pack Minimal Cookbook](../cookbooks/review_pack_minimal.md)
@@ -50,6 +52,10 @@ deferred.
    - Read this before external sharing to check target readers, contribution
      framing, figures, evaluation evidence, and claims boundaries.
 
+Previous drafts V3 and V2 remain useful supporting background when reviewing
+how the technical note was compressed and polished, but V3.1 is the current
+canonical draft.
+
 ## Target Readers
 
 Primary readers:
@@ -86,8 +92,8 @@ implemented contributions:
 
 1. A local verify-first / fail-closed Review Pack artifact model for signed
    agent evidence bundles.
-2. A dual human/agent review surface: `summary.md` plus `manifest.json`,
-   `receipt.json`, and `findings.json`.
+2. A dual human/tool-using-agent review surface: `summary.md` plus
+   `manifest.json`, `receipt.json`, and `findings.json`.
 3. Stable `RP-CHECK-*` reviewer checklist IDs and bounded findings/severity
    model.
 4. Conservative safety boundaries: no private key copying, no network
@@ -143,15 +149,17 @@ external sharing language.
 
 ## Next Writing Step
 
-Recommended next phase:
+Recommended next phase after this index update:
 
 ```text
-P50 Review Pack V0.3 white paper polish planning
+P54 Review Pack V0.3 white paper index post-merge sanity
 ```
 
-P50 should decide whether to prepare a V3.1 draft, refine diagrams, select the
-final abstract for external sharing, and decide whether and when to create a
-Zenodo technical report. arXiv and workshop submission should remain deferred.
+After post-merge sanity, the next writing-planning decision should be whether
+to prepare a concise Chinese summary or to plan a Zenodo technical report. The
+current recommendation is to consider Chinese summary planning first. Zenodo
+technical report, arXiv submission, and workshop submission should remain
+deferred until a separate readiness decision.
 
 Do not make AI Act Pack implementation the next step.