A systematic review confirms a significant research gap: no existing publication proposes a standard for documenting the intellectual provenance of AI-augmented scientific ideation. Computational provenance is mature; ideation provenance is absent. Policy urgency (NIH NOT-OD-25-132, Genesis Mission EO) and the Karpathy LLM Wiki ecosystem create the conditions for a timely, novel contribution.
Computational provenance exists for data and code. No paper bridges to ideation — tracking prompt strategies, concept evolution, and human-AI dialogue.
NIH refuses AI-developed ideas as original (NOT-OD-25-132). Genesis Mission demands dataset provenance but omits ideation documentation.
Five open-source implementations (April 2026) provide viable infrastructure. Knowledge compounding validates economic returns of persistent documentation.
2026 PubMed papers independently call for AI disclosure standards. JCTS is the right venue — translational research where attribution matters most.
No paper proposes or demonstrates provenance tracking for prompt strategies, AI model versions, iterative concept refinement, or human-AI creative dialogue.
Without process provenance, compliance with NOT-OD-25-132 is ad hoc and unverifiable. The Genesis Mission's partial coverage of provenance creates a policy gap our paper addresses.
5,448★ — Persistent compounding wiki based on Karpathy's pattern
1,647★ — Multi-platform knowledge base builder
1,482★ — AI agents building digital brains through Obsidian
1,280★ — Source-in, wiki-out. The compiler pattern is most provenance-native
The LLM Wiki already captures AI-human dialogue, interlinked knowledge evolution, and timestamped contributions. Adding provenance metadata is incremental, not revolutionary.
| Research Line | Key Finding |
|---|---|
| AI-Augmented Ideation | LLMs generate novel ideas but struggle with feasibility — need systems to track evaluation and refinement (Liu 2025, ResearchCube 2026) |
| AI Attribution | AI-generated code can be fingerprinted (Ghaleb 2026). AI exhibits "fluid agency" requiring human sponsorship (Mukherjee 2026) |
| Citation Failures | Existing citation frameworks are inadequate for AI collaboration (Shukla 2025) |
| Auditable AI | Schema-constrained approaches produce verifiable biomedical outputs (PubMed 2026) |
None of these approaches addresses documentation of the creative process itself. Process provenance is the missing layer across all adjacent fields.
The JCTS audience bridges discovery to practice — precisely where attribution integrity and human accountability matter most. A demonstration paper here lands with maximum impact.
Select implementation substrate. Evaluate llm-wiki-compiler vs. claude-obsidian for the demonstration. The compiler pattern (source-in, wiki-out) is more provenance-native.
Draft Introduction and Background. These sections are literature-driven and can be written directly from this gap assessment.
Implement provenance extensions. Add structured logging, human attestation, and immutable audit trail to the chosen LLM Wiki fork.
Select demonstration case study. Ideally the JCTS manuscript development process itself (meta-demonstration), or a representative Duke translational research workflow.
Second-round literature search. Re-run prior to submission to capture any late-breaking 2026 publications in this rapidly evolving space.
Target submission: JCTS, 8–12 week timeline from initiation.
Tier guide: Tier 1 = Primary institutional source (NIH, White House, GitHub ecosystem, PubMed) · Tier 2 = Preprint or trade publication — validated but not peer-reviewed · Tier 3 = Breaking news / single-source — verify independently
Generated May 24, 2026 · DeepSeek V4 Pro · Gambit / brief-to-slides v2.0