Ownership Record: Who Made What in This Project
An honest accounting of the distribution of work between the human author and Claude across the development of these workshop materials. Written in the spirit of the disclosure principles the materials themselves advocate.
This document applies the framework from B.ownership.md to the project that produced it.
Why this document exists
These materials teach researchers to assess and disclose AI's role in their work. Practising that on the materials themselves is the honest thing to do — and makes the point more credibly than any lecture about it.
This is also a useful record for when the materials are published (GitHub Pages, mini-books): attribution should be accurate, not gestural.
Modes of collaboration used in this project
Rather than scoring each document, it is more useful to describe the distinct modes of collaboration that produced them.
Mode 1: User-authored
The user wrote the document independently. Claude was available but not the drafter.
Documents:
-
A2.desktop-basics.md -
A3.code-basics-non-programmers.md(session 30: Node.js prerequisites section replaced with two-option intro — Desktop Code tab vs. terminal install; install commands updated to native scripts; update section simplified to auto-update — Mode 2 additions to an otherwise Mode 1 document) -
A4.conceptual-vocabulary.md(session 33: "RAG (Retrieval-Augmented Generation)" glossary entry added, closing a gap found when the user asked whether the book covers RAG — user directed, Claude drafted; Mode 2 addition to an otherwise Mode 1 document) -
A5.shortcuts-daily-usage.md -
A6.zero-coding-workflows.md -
A.concept.global-vs-local.md -
A.token.management.md -
A.setup.windows-wsl.md(session 30: Node.js install step removed, nativecurlinstall script replaces npm, native Windows section updated to PowerShellirminstaller, auto-update note added — Mode 2 additions to an otherwise Mode 1 document) -
A.adjacent.gemini.md -
A.adjacent.tools.md(session 13: oh-my-openagent section added by Claude from user-provided source notes — Mode 2 addition to an otherwise Mode 1 document; session 25: "Alternative coding harnesses" subsection added by Claude from user-directed web research on harness concept — further Mode 2 additions; session 31: vendor-portability paragraph added closing the harnesses subsection — user identified the gap, Claude drafted — Mode 2; session 33: Hermes paragraph added — user named the tool and its URL, Claude fetched hermes-agent.ai and drafted the entry; a second candidate, ncm.opentechlab.cz, was investigated and deliberately excluded at the user's direction — Mode 2) -
C.resources.md— curated reading list; user selected and annotated the sources; structure and one-line rationale text are user-written -
A14.skills-for-researchers.md -
A15.agent-personalities.md -
A16.personal-life-management.md -
A.obsidian-logseq.md -
start.md(initial version)
Ownership: User — ideas, structure, language.
Mode 2: Claude-drafted from user brief
The user identified the topic and provided a brief (sometimes a sentence, sometimes a list of points to cover); Claude drafted the document; user reviewed and accepted with light or no editing.
Documents:
-
A1.desktop-vs-code.md— initially drafted by Claude; user subsequently revised to add the three-way Desktop/Cowork/Code comparison when Claude Cowork became relevant. Language is primarily Claude's; the three-way framing and the Cowork tier are the user's intellectual addition. (Session 30: expanded to four tools — Claude Code Web added as fourth surface; new section, updated comparison table, revised How-to-choose guidance; triggered by official docs check — Mode 2 addition.) -
A.issue.upload-dance.md -
A.concept.under-the-hood.md -
A.concept.agents.md— framing is Claude's; the "never modify originals unsupervised" rule for archival researchers was user-directed -
A.setup.settings-local.md— triggered by a real problem discovered mid-session (WebSearch blocked); Claude diagnosed and fixed it, then wrote the doc -
A7.working-with-pdfs.md,A8.working-with-docx-xlsx.md,A9.markdown-project-memory.md,A.markdown-central.md,A10.claude-and-zotero.md -
A.markdown.history.md -
B.usecases.md— 8 scenario sketches; user provided the scenario list and DISSINET framing context -
B.experience.md— user provided the core concepts (control/ownership axis, joy/curiosity, overwhelm/FOMO, real vs. anxiety-driven productivity, work-life balance); Claude structured and wrote -
B.ownership.md— user framed the question; Claude structured and drafted -
A.issue.privacy-security.md— user identified the gap; Claude drafted -
A.issue.context-scope.md— user identified the gap; Claude drafted -
A.issue.model-selection.md— user identified the gap; Claude drafted. (Session 30 corrections: model ID updated fromclaude-opus-4-6toclaude-opus-4-8; context window claim corrected from "same ~200k across all three" to differentiated 1M/1M/200k — triggered by checking official docs. Mode 2 corrections.) -
A.concept.memory.md— user identified the gap; Claude drafted -
A.issue.personalisation.md— user identified the gap; Claude drafted -
A.issue.team-claude.md— user identified the gap; Claude drafted -
B.trust.md— user provided conceptual framing; Claude drafted -
A.issue.bounding.md— user provided conceptual framing; Claude drafted -
B.autonomy.md— user provided conceptual framing and three specific directions; Claude drafted -
B.team-ai.md— user provided conceptual framing; Claude drafted; user provided DISSINET team context via interrogation; Claude revised -
B.lifecycle.md,B.lifecycle.0.iteration.md,B.lifecycle.1.creativity.md,B.lifecycle.2.literature.md,B.lifecycle.3.datacapture.md,B.lifecycle.4.dataanalysis.md,B.lifecycle.5.manuscript.md— user provided the core claim, the organizing insight (engineering-like vs. interpretive), the subdocument structure, the iterative/non-waterfall framing, the "fail quickly and document" principle, and the 5↔1 proposal-writing connection; Claude drafted all seven -
_history.md— Claude drafted from the conversation record -
_history.archive.md— Claude extracted sessions 1–16 from_history.mdand wrote the archive; user approved the split -
_ownership.md— this document; same mode -
A.issue.slack-workspace.md— user identified topic and two workflow scenarios; Claude drafted -
B.epistemics.md— user specified the four risks and counter-practices (including cross-model checking); Claude drafted -
C.dangers.md— user commissioned summative risk map; Claude drafted from cross-referencing existing documents -
B.adoption-spectrum.md— user proposed the concept (spectrum from occasional chatbot use to agent orchestration) and sketched the five positions in a planning session; Claude drafted the document with the level descriptions, risk distribution framing, and "Level 2–3 is exactly right" section -
C.leveling-packages.md— user directed the three-part structure (conceptual shift / first experiment / practice) and the transition framing; Claude drafted all four packages and the closing "you don't have to level up" section -
C.why.md— user identified the need (entry-level motivations document) and the two-part structure (reasons to start; reasons to level up); Claude extracted and synthesised from existing B/C documents and drafted all entries -
C.tasks.md— user identified the need (task reference by adoption level) and the level-organised structure with "what AI does / what human retains" format; Claude extracted tasks from existing scenarios and documents and drafted -
d.plan.md— user specified the workshop structure (2.5h, four blocks, installation + repo clone + new project + PDFs), the key constraints (Windows native, ≤10 participants, solo presenter, private repo), and the demos to script; Claude drafted the full agenda, presenter notes, pre-workshop checklist, and demo prompt scripts -
D.tutorial.setup.md— user specified: Windows native path, terminal basics section, winget + fallback installers, WSL2 hint; Claude drafted the full step-by-step guide including troubleshooting section -
D.tutorial.firstproject.md— user specified: two-part structure (clone + explore; new project from scratch), start.md template, PDF conversion as deepest exercise, reading note creation; Claude drafted all content including verbatim prompts and the template -
B.centroid-periphery.md— user provided the key reframe (center = legitimate, navigation = the skill); Claude drafted -
A.issue.plan-mode.md— user identified the gap; Claude drafted -
B.TH.personal.use-cases.md— user provided raw notes (_TH.microcases.md) and answered clarifying questions; Claude digested, structured, wrote, and anonymized from source directories; a richer-source-material Mode 2 -
_microcase.template.md— user described the 4-part structure; Claude created the template -
CLAUDE.md— Claude drafted based on accumulated project knowledge; user approved -
.claude/commands/update-meta-docs.md— Claude designed and wrote from user's request for a periodic update mechanism -
.claude/settings.json— Claude wrote the Stop hook; user approved -
research-lifecycle.excalidraw/research-lifecycle.png— user commissioned the diagram; Claude generated via the Excalidraw skill with iterative render-fix cycles -
_index.md— user identified the need and described the purpose (quick-search, wiki hover, network term layer); Claude extracted terms from all documents, wrote descriptions, and structured the index -
C.philosophy-experience.md— user commissioned a consolidating glossary of the distinctive concepts running through the project; Claude extracted named framings from all B and C documents and wrote the entry descriptions; the selection and framing of which concepts warranted a glossary entry was Claude's editorial judgement from the user's brief -
build/build.py— user provided a detailed design plan (two-pass architecture, file-filter rules, category/colour mapping, edge deduplication, description extraction, term-index output); Claude implemented the full script. Extended in session 16 withget_version()(git-derived auto-increment) anddocs/version.jsonoutput; Mode 2. -
build/requirements.txt— Claude produced from the script's imports -
docs/index.html— (session 19) completely redesigned as a standalone landing page using thefrontend-designskill. User specified the two-column layout concept, level teaser requirement, and split-screen link behaviour; Claude designed and implemented the full page including typography, layout, level rows, and mobile responsive handling. Mode 2. -
docs/map.html— (formerlydocs/index.html) user specified the entry-point design (force-graph, full-viewport, tooltip, guidance-panel slot, error state); Claude wrote the HTML and JavaScript. Subsequently extended across sessions 12–16 with meta-doc nodes, home panel, carousel, version fetch, and split-screen navigation; extended (session 19) with level nodes injection, "Your level" home-panel section, postMessage lightbox receiver, and hash-based auto-open. All additions Mode 2. -
docs/level-0.htmlthroughdocs/level-4.html— five standalone level pages (session 19). User provided the level content (fromB.adoption-spectrum.mdandC.leveling-packages.md) and the design brief ("character sheet meets research journal"); Claude designed and implemented all five pages including the watermark numeral, level nav strip, risk card aesthetic, and Level 4 "you've arrived" variant. Mode 2. -
docs/style.css— user specified the two-mode visual design (map page dark, doc page light) and reserved guidance-panel slot; Claude wrote all CSS. Extended in session 12 with home panel styles; extended in session 15–16 with diagram card and carousel styles, version display, document footer flexbox; Mode 2. -
C.cheatsheet.md— user proposed the document type (one-page reference card); Claude drafted from A5, A1, A.issue.privacy-security, and project knowledge -
C.calibration.md— user proposed the calibration frame and section structure; Claude drafted using Pepinsky's execution/interpretation axis, drawing on C.why, C.dangers, A.critical.limitations, B.adoption-spectrum -
C.ethics-compact.md— user proposed the three-decision structure; Claude drafted from A.issue.privacy-security, E.muni-guidelines, E.journal-funder-policies, B.ownership -
C.prompts.md— user proposed the prompt gallery concept and five category structure; Claude drafted all 20 prompts drawing on B.usecases, C.tasks, A.markdown-central, A9, and DISSINET knowledge -
C.workflows.md— user proposed four specific workflows; Claude drafted all four step-by-step narratives from B.usecases, A.markdown-central, C.prompts, and the D tutorial documents -
A.markdown-central.md(session 14 correction) — markitdown installation commands corrected from baremarkitdownto"markitdown[pdf]"; warning blockquote added; discovered by attempting a real conversion during session work -
A.setup.windows-wsl.md(session 14 correction) — WSL Step 5 install command and Windows-native troubleshooting note updated to reflect[pdf]requirement -
agents-diagram.excalidraw/docs/assets/agents-diagram.png— user provided a design plan (two-panel: agent cycle + supervision modes); Claude generated via the Excalidraw skill with iterative render-fix cycles -
adoption-spectrum-diagram.excalidraw/docs/assets/adoption-spectrum-diagram.png— user specified the 5-level vertical ladder with "key threshold" annotation at Level 2; Claude generated via the Excalidraw skill -
privacy-dataflow-diagram.excalidraw/docs/assets/privacy-dataflow-diagram.png— user specified three parallel swim-lanes (Desktop/API/Local) with per-lane annotations; Claude generated via the Excalidraw skill -
centroid-periphery-diagram.excalidraw/docs/assets/centroid-periphery-diagram.png— user specified the concentric zone map (center blue, periphery amber dashed); Claude generated via the Excalidraw skill -
remotion-history/(package.json, src/index.ts, src/Root.tsx, src/ProjectHistory.tsx) — user commissioned a video about the project's development history using_history.mdas source; Claude implemented all Remotion code including the 7-scene structure, animation helpers, and stat counters -
A.issue.research-data-memory.md— user identified the gap (no document on compartmentalising project memory for data-heavy research) and specified the five problem areas (data description, analysis plan, transformation logic, variants, proposal linking); Claude designed the three-layer model, selected trialinter as the primary example after exploring the _logic/ directory, and drafted all content including the file-role descriptions and practical principles -
C.project-history.md— user commissioned a blog-article history of the project told from Claude's perspective with the brief "write it as Claude"; Claude selected the five narrative moments (reconstruction problem, research agents, documents that surprised, the CLAUDE.md timing, the graph), drafted all prose, and made all editorial choices about what to include and how to frame it (a Mode 2 document with more editorial latitude than usual — the brief specified form and voice, not content) -
_deck/*.png(21 slide images) — user commissioned extraction fromnotebooklm-slides-v2.pdf; Claude rendered all pages via PyMuPDF, read each slide visually, proposed descriptive filenames from content analysis, and embedded each image in the knowledge document it best illustrates; 22 insertions across 20 source files -
_github.pages.plan.md— user specified the publication target (DISSINET org, URL slug); Claude drafted the step-by-step plan, identified the privacy/visibility constraint (private repo → Pages requires Team plan or public repo), wrote the verification checklist -
docs/C.media.html— (session 21) user specified the content (NotebookLM podcast + infographic, playable and zoomable); Claude designed and implemented the full page including the podcast player, lightbox JS, dark-theme styling, and footer navigation. (Session 22) substantially enhanced with PDF slide deck iframe, section icons, and "How This Was Made" automation box; user identified each addition, Claude designed and implemented. Mode 2. -
C.start-here.md— user identified the need (orientation document for self-directed readers, five prerequisite concepts); specified the "Fail quickly" blockquote with amber styling and links to ethics/privacy/ownership docs; Claude drafted all five sections and the amber blockquote callout -
A.issue.python-basics.md— user identified the gap; Claude drafted -
A.issue.nodejs-basics.md— user identified the gap and the key clarification (Claude Code no longer requires Node.js but npm/npx are still needed for skills and MCP); Claude drafted -
B.time.md— user identified the framing (capacity ceiling vs. schedule compression, Parkinson's Law for AI); Claude structured and drafted all sections; cross-references to B.experience, C.calibration, and C.why added at user direction -
C.rules.md— user identified the need (PLoS-format ten simple rules document); Claude drafted all ten rules, the failure-mode structure for each, and the closing note grouping rules by type (setup/process, epistemic, sustainability) -
A.issue.bounding.md(session 23 addition) — "When the form is the bound" section: user directed that GAČR template discovery should be added as a new principle; Claude identified the principle (external official structures as prompting context), wrote the full section, added the diagnostic entry, and updated A.issue.context-scope with a reciprocal link -
E.plan.md— user directed a strategic assessment of the near-finished project; Claude assessed the project state, identified the four content gaps and five development directions, and drafted the full document including the "What not to add" section -
A.working-with-images.md— user identified the multimodal gap; Claude drafted, covering capabilities, limits, DISSINET-specific workflows, and practical prompts -
A.issue.prompt-iteration.md— user identified the prompt debugging gap; Claude drafted, including the three root-cause framework, iterate-vs-restart decision, and meta-prompt technique -
D.tutorial.first-month.md— user identified the post-workshop integration gap; Claude drafted the week-by-week guide and abandonment-pattern analysis -
A.issue.costs-quotas.md— user identified the economic layer gap; Claude drafted covering Pro quota, API economics, token estimation, and practical decision rules -
_gacr.standard.proposal.md— user directed extraction from the Tender Document PDF; Claude fetched the PDF, extracted the full proposal structure, wrote the provenance callout, and produced the full reference document -
C.workflows.mdWorkflow 5 (session 24) — user identified syntopical reading (Adler) as the organising concept; Claude designed the two-mode table, intermediary document folder structure, session-by-session protocol, and CLAUDE.md template; user accepted -
D.handout.md— user specified the one-page format and the key content categories (terminal commands, starter prompts, CLAUDE.md template, troubleshooting table, after-today link); Claude drafted all content and rendered the PDF via weasyprint -
docs/assets/agentic-loop.svg— downloaded from Anthropic CDN; recoloured to site dark palette by Claude; inserted intoA.concept.under-the-hood.mdwith source citation -
docs/assets/data-boundary.svg— user identified the gap (official diagram does not show data residency); Claude hand-crafted the SVG with two labelled zones (YOUR MACHINE / ANTHROPIC SERVERS), payload arrow, and "Local ≠ private" warning box -
d.plan.md(session 24 overhaul) — user identified the three psychological pressure points (installation, terminal, generic output); Claude designed the seven targeted interventions and wrote all additions including the presenter psychological arc section -
B.epistemics.md,B.autonomy.md,C.calibration.md,A.concept.agents.md,B.centroid-periphery.md(session 24 Gottweis additions) — user directed citation of five relevant passages from Gottweis et al. 2025; Claude identified the most fitting insertion point in each document, wrote the contextual framing, and formatted the citation -
A4.conceptual-vocabulary.md(session 25 "Harness" section) — user identified the concept and directed web research; Claude drafted the full section including the model/harness separation analogy, five-harness comparison table, and Martin Fowler reference; user approved. Also: diagram updated to add harness as outermost layer — Claude's editorial addition accepted without direction. Mode 2 additions to an otherwise Mode 1 document. -
D.tutorials.md— user identified the need for a navigation index for the three D tutorials; Claude drafted the numbered progression structure and time estimates; user approved -
build/build.py(session 26 multi-book refactor) — user directed the architectural design (BOOKS registry, per-book output dirs, cleanup step, redirect generation); Claude redesigned and rewrote the full script -
build/publish.py(session 26 rewrite) — user identified the problem (SFTP-only publish leaves stale remote files); Claude diagnosed and rewrote with rsync-style sync semantics,--dry-runflag, and auto-build step -
build/static/map.html,build/static/level-0..4.html— static HTML files recovered from git history, patched for book subdirectory CSS path, now tracked as build sources; user identified the recovery need, Claude executed -
research-augmented/CLAUDE.md— book-specific CLAUDE.md created; Claude drafted from existing root CLAUDE.md content adapted for new path structure; user approved -
CLAUDE.md(session 26 rewrite) — root CLAUDE.md rewritten as repo-level overview of multi-book structure; user specified the architecture, Claude wrote -
.claude/commands/update-meta-docs.md(session 26 update) — updated to detect active book from changed files and route to<book>/_meta/; Claude designed and wrote the book-detection step -
.claude/commands/update-index.md(session 26 update) — path updated to<book>/_meta/_index.md; Claude wrote -
A.issue.session-endings.md— user generated the observation mid-session (asking "could we generalise this to a principle?") after noticing that discovered session output would have been lost without a deliberate audit; Claude drafted the document, named the planned/discovered distinction, and wrote the pre-close prompts; user approved -
build/static/index.html(session 27 CSS repair) — user identified visual bugs via browse-skill screenshots; Claude diagnosed the CSS ordering bug (media queries before base styles), fixed all layout issues, and iteratively verified via computed styles and screenshots; Mode 2 additions to an already-Mode-2 document. (Session 33: ERC/Horizon 2020 funding acknowledgment line added to thehero-provenanceblock, exact required wording supplied by the user — Mode 1 addition, Claude only placed it.) -
A.markdown.token-efficient-docs.md— user identified the topic ("optimize meta-docs for LLMs, token efficiency") in a single-sentence commission; Claude scoped the seven principles, drafted the full document including before/after examples, the lean stack summary, and the pre-save checklist; user accepted. Mode 2. -
A9.markdown-project-memory.md(session 28 additions) — user approved two additions after evaluating source PDFs: "Keeping CLAUDE.md alive: three tools" section (/reflection, /insights, evolution rhythm) and the expanded practical-tips section (200-line limit, communicate-intent principle with before/after table); Claude drafted both additions; user accepted. Mode 2 additions to an existing Mode 2 document. -
A.concept.global-vs-local.md(session 28 addition) —CLAUDE.local.mdparagraph added; user directed, Claude drafted; Mode 2 addition. -
A.setup.settings-local.md(session 28 addition) —rules/folder section added; user directed, Claude drafted with transcription-conventions example; Mode 2 addition. -
A.issue.research-wiki.md(session 29) — user identified the topic (Karpathy LLM Wiki gist relevance to book); Claude evaluated the gist and comments thread, identified which insights were new to the book, and drafted the full document including the error-compounding graph analysis, @import wiring section, and decision-support framing drawn from specific comments; user approved additions from the ErikEvenson and lkishfy threads. Mode 2 with richer source material (external gist + comments thread) — closer to Mode 3 in research content but user-directed rather than agent-researched. (Session 33: the pattern was named in the document's substance since session 29 but never explicitly credited to Karpathy in text — user asked about "llm-as-wiki" and Graphify without knowing the document already covered the pattern; Claude added a paragraph quoting the gist directly and a new Graphify paragraph. The first Graphify draft overstated a code-only limitation; corrected after the user pushed back and Claude re-checked the tool's actual README. Mode 2 additions, self-corrected within the session.) -
C.llm-as-reader.md(session 29) — user identified the need for a synthesis document on the "advanced LLM as reader" concept after evaluating SwarmVault vs. folder+Claude Code; Claude identified the spectrum framing, drafted all content including the calibration table and "working responsibly at the reads end" section; user approved. Mode 2. -
build/excalidraw-to-png.py(session 29) — user identified the need (broken diagram PNGs; no existing export script); Claude diagnosed the CDN-blocking issue, chose the localhost HTTP server approach, and implemented the full script; user approved. Mode 2. -
B.knowledge-curation.md— user identified the framing (tribal knowledge problem; Wikipedia materialised-view analogy; DISSINET-specific institutional memory as context); Claude structured and drafted. Mode 2. (Session 33: RAG gloss and link added at the document's first RAG mention; two dangling links to a never-existentA.projects.mdcorrected toA9.markdown-project-memory.md— Claude found the broken links while making the RAG fix, user confirmed the redirect target. Mode 2 additions.)
Ownership: Ideas substantially co-generated; language primarily Claude's; structure primarily Claude's with user steering.
Mode 3: Research agent + Claude synthesis
The user commissioned web research with a defined brief; a background Claude agent ran the searches and produced raw findings; Claude synthesised findings into a structured document; the user exercised editorial oversight and accepted.
Documents:
-
A11-A13.research-examples-raw.md— raw agent output, not synthesised -
A11.examples-claude-code-researchers.md -
A12.examples-claude-desktop-research.md -
A13.examples-dissinet-usecases.md -
A.workflows.notes-reading-writing-raw.md— raw agent output -
A.workflows.notes-reading-writing.md -
E.journal-funder-policies.md -
E.muni-guidelines.md -
E.cuni-researcher-recommendations.md
Ownership: Research brief and editorial direction are the user's. The actual research — finding the sources, identifying the key figures, selecting the relevant findings — was performed by the agent. The synthesis structure and language are Claude's. The facts derive from sources the agent found; the framing of what matters derives from Claude's interpretation of the user's brief.
-
A.setup.zotero-mcp.md— user identified the specific tool and GitHub URL; Claude ran a research agent to fetch repository documentation, issues, and installation details; Claude drafted the setup guide from findings -
A.literature-discovery.md— user identified the gap (no single document assembles the discovery workflow); Claude drafted from existing documents and synthesised the 6-step workflow -
A.skills-ecosystem.md(additions) — user commissioned web research and provided two PDFs (Medium article, Reddit thread); Claude read PDFs and synthesised insights into new sections ("Two principles before you browse", "Creating your own skills"); the distributional convergence concept and Reddit community consensus were derived from the source documents; research-specific examples for DISSINET were Claude's synthesis from the user's framing -
A.skills-ecosystem.md(session 13 additions) — user provided pre-gathered source notes (_sources/scientific.skills.md); Claude integrated two new discovery channel entries (Reddit skills thread, Medium practitioner list) and corrected the alirezarezvani skill count -
A11.examples-claude-code-researchers.md(session 13 additions) — user provided source notes; Claude drafted two new sections (Agents Research Lab multi-agent account; Google DeepMind AI co-scientist paradigm with arXiv reference and connection to existing B.lifecycle.1.creativity framing) -
C.resources.md(new "CLAUDE.md and the.claude/folder" subsection) and_meta/note.claude-vs-chatgpt-scoping-memory.md— three pre-gathered files (two blog-post PDFs, one saved AI comparison transcript) had been sitting in a stray root-level_sources/directory that predated this book's per-book conventions; Claude read all three, wrote proper citation entries for the two externally-published pieces, and relocated the un-linkable transcript into_meta/with a provenance note rather than discarding it; user directed the filing decision ("transform to repo convention first")
This is the mode with the most diffuse ownership. The user cannot independently claim credit for finding Pepinsky, Hall, or Berry — the agent found them. The user can claim credit for commissioning the right questions and judging what was useful.
Mode 4: Structural and editorial decisions (throughout)
Across all modes, the following remained entirely the user's:
-
The project definition: Audience (DISSINET researchers, non-programmers), purpose (3h workshop), scope (document-heavy research workflows), and the "one takeaway" framing
-
All phase and scope decisions: What to include, what to defer, what to cut
-
The A/B/C/D/E structure and what belongs in each phase
-
The E2 student book central theme: "You need to own the result" — this framing was the user's invention, not Claude's suggestion
-
The three-way Desktop/Cowork/Code comparison (revision of A1)
-
The "archival researcher never modifies originals" rule (addition to A.concept.agents)
-
All go/no-go decisions on document quality and inclusion
-
The decision to add
## Relatedcross-links to all documents -
The D1 GitHub Pages + network visualisation concept
Overall ownership assessment
Applying the dimensions from B.ownership.md:
| Dimension | User | Claude |
|---|---|---|
| Project framing, audience definition, scope | Primary | Minimal |
| Structural decisions (what to include, phase structure) | Primary | Advisory |
| Core ideas and concepts | Shared — user named the problems; Claude structured the frameworks | Shared |
| Research findings (A11–A13, E-docs) | Commissioned and curated | Executed |
| Language and prose | ~30% (Mode 1 docs) | ~70% (Mode 2 and 3 docs) |
| Evaluative judgement (what is good enough) | Primary | None |
Plain statement: The user directed this project and wrote roughly a third of the documents independently. The remaining two-thirds were drafted by Claude from user-provided briefs, commissions, or topic identifications — and accepted with light editorial revision. The ideas in the Claude-drafted documents are genuinely collaborative: the user framed the questions that shaped the documents, and Claude structured the answers. The language is predominantly Claude's.
What this means for attribution and disclosure
If these materials are published under the user's name:
Accurate disclosure: "These workshop materials were developed in collaboration with Claude (Anthropic). The project structure, editorial decisions, and approximately one-third of the documents were produced by the author independently. The remaining documents were drafted by Claude from the author's briefs and commissions, and accepted following editorial review. All research findings (external sources, policy documents) were obtained via AI-assisted web research agents working from author-defined briefs."
What the user can claim without qualification: The project concept, audience framing, scope decisions, the E2 "own the result" framing, the three-way tool comparison, and all Mode 1 documents.
What requires qualified attribution: The Mode 2 documents — the ideas are collaborative, the language is Claude's. The Mode 3 documents — the research was AI-executed; the user commissioned and curated.
A note on the meta-level
This document is itself a Mode 2 product: the user identified the need for it and the question it should answer; Claude drafted it. The ownership assessment it contains is Claude's interpretation of the conversation record and _history.md. The user should verify that the Mode 1 document list is accurate and that the overall characterisation matches their experience of the collaboration.
If it does not — that discrepancy is itself informative.
Related
-
B.ownership — the framework this document applies; the ownership dimensions and review prompts
-
B.experience — the experiential dimension of ownership; this document is the concrete accounting that B.experience calls for
-
_history.md — the development record this document complements; _history covers what was done, _ownership covers who