Skip to content

docs: plan durable source-adapter curation as Milestone 5 - #13

Merged
leej3 merged 3 commits into
mainfrom
agent/plan-milestone-5-adapter-curation
Aug 18, 2026
Merged

docs: plan durable source-adapter curation as Milestone 5#13
leej3 merged 3 commits into
mainfrom
agent/plan-milestone-5-adapter-curation

Conversation

@leej3

@leej3 leej3 commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

AI-generated draft — not reviewed by John

Summary

  • distinguish Git/DataLad execution evidence, PAV assertion provenance, durable human dispositions, and disposable adapter caches;
  • document a two-phase static workflow for proposal, explicit human decision, reconciliation, and final-head review;
  • record the accepted HR-207/M4-I015 safety defaults while leaving serialization and common adapter interfaces exploratory;
  • add a proposed Milestone 5 plan, engineering decision gates, and a two-adapter acceptance matrix for Zotero and dump-research-info.

Why

A rejected source candidate currently leaves no durable fact when no metadata record is merged, so a later adapter run can ask a human to make the same decision again. The proposed exploration develops decision memory without treating caches, PAV, SSSOM mappings, or pull-request closure as a rejection ledger.

Impact and boundaries

Milestone 5 remains proposed rather than activated. The plan preserves the ordinary single-repository/static workflow, requires no persistent service or bot, keeps the production site read-only, and extracts shared adapter behavior only after both adapters demonstrate it.

Development and operations skills were used as non-normative review guidance; supported behavior remains defined by repository-owned specifications, fixtures, tests, and release evidence.

Validation

  • pixi run format-docs
  • pixi run check-format
  • git diff --check
  • rebased onto origin/main at fe01e297d3d22d1690bf891b40eaab36595cea9e

leej3 added 3 commits August 18, 2026 17:17
Separate execution provenance, assertion provenance, durable human dispositions, and disposable cache state. Define a two-phase, one-PR workflow and evidence-driven exit criteria for the adapter exploration.

Co-Authored-By: Codex Desktop 26.810.52044 (runtime codex-cli 0.148.0-alpha.9) / gpt-5.6-sol <codex@openai.com>

Codex-Reasoning-Effort: ultra
Record the reviewed boundary between Lite safety defaults and adapter-specific identity and fingerprint configuration.

Keep the serialized decision format and common adapter interface exploratory until two adapters demonstrate the contract.

Co-Authored-By: Codex Desktop 26.810.52044 (runtime codex-cli 0.148.0-alpha.9) / gpt-5.6-sol <codex@openai.com>

Codex-Reasoning-Effort: ultra
Define the two-adapter exploration, exact planning coordinates, repository ownership, decision gates, and static review transaction.

Add a proposed decision register and acceptance matrix without activating the milestone or freezing an adapter schema, CLI, or storage contract.

Co-Authored-By: Codex Desktop 26.810.52044 (runtime codex-cli 0.148.0-alpha.9) / gpt-5.6-sol <codex@openai.com>

Codex-Reasoning-Effort: ultra
@leej3
leej3 marked this pull request as ready for review August 18, 2026 22:19
@leej3
leej3 merged commit 2d32c4b into main Aug 18, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant