coulomb/coulomb-research
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Resolve CR-000-X005 and CR-000-X007 (CR-WP-0005 T01–T02)

Browse source 
Mark C001 as a loose conjecture and sharpen C005 to the manuscript's meta-level cycle without new evidence or a supported state. Record that Added by is the drafter, and add Position origin on each claim.

Assistant: grok
Assistant-Session: 01a10946-16b2-7771-88ac-c6bc305423b3
This commit is contained in:
tegwick 2026-10-05 01:42:10 +02:00
parent b5892748d7
commit 4f6384808e
7 changed files with 245 additions and 55 deletions
Download patch file Download diff file Expand all files Collapse all files

43
docs/ResearchArtifactConvention.md
View file

@ -147,10 +147,45 @@ follows `seed/PublicationInterface.md` §4 and is out of scope for M0/M1.
Every claim, evidence item, and criticism entry should record, inline in its
own file entry, at minimum:
- the authoring actor (human or agent, per `seed/CoulombResearchKernel.md`
§2.1/§4), written as `human:<name>` or `agent:<name>`,
- the date it was added,
- for agent-authored entries, the model/toolchain if relevant.
- the actor who transcribed or drafted the entry text (human or agent, per
`seed/CoulombResearchKernel.md` §2.1/§4), written as `human:<name>` or
`agent:<name>`,
- the date that text was added,
- for agent-drafted entries, the model/toolchain if relevant.
On a claim entry, that drafter/transcriber relation is the `Added by`
field. **`Added by` means who wrote the words of the entry. It does not
mean who originated the position, and it does not mean who approved the
commit.** Approval is a different relation: a human can retain commit
approval without being the source of the proposition and without being the
drafter (`manuscript.md` §7 for CR-000). Do not record approval in
`Added by`.
A claim entry must also record `Position origin`.
`seed/CoulombResearchKernel.md` §4 treats "source asserts P" and "actor
asserts P" as non-interchangeable, so a single drafter field cannot stand
in for both. Use one of:
- `source: <path>` — the position is a transcription or close restatement
of that source. Name the source. Do not attribute the position to the
transcriber.
- `actor: <id>` — a Coulomb actor originated the position in this entry,
rather than taking it from a source. This is "actor asserts P". Use it
only when the record supports origination, not as the default for
whoever typed the file.
- `mixed` — name the source the position comes from and the actor who
added an operational reading the source does not already state. Say
which is which.
- `unrecorded` — the files do not support the distinction. Do not guess.
Do not overwrite `Added by`, and do not delete a recorded origin, when a
later actor edits an entry. Name that later actor and date on the wording
they added, and append the change to `revision-log.md`.
Evidence and criticism entries are not claim positions. Their `Added by`
or `Critic` field likewise names who wrote that entry. When an evidence
entry draws on a source, its `Source` field records that source; it does
not make the drafter the origin of a claim.
This is a lightweight, file-embedded application of the kernel's provenance
requirement (`seed/CoulombResearchKernel.md` §4) — it does not introduce a