Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

nanopubs/ — FORRT nanopublication chain workspace

LifeWatch ERIC

This directory holds the field-by-field drafts of the FORRT chain, plus the registry of published URIs. The chain is published manually on https://platform.sciencelive4all.org — Claude does not publish; Claude drafts each step in drafts/, you review and copy-paste into the platform UI, and the resulting URI goes into PUBLISHED.md.

The chain

A complete FORRT chain is six steps published in order. Step 1 has three alternative anchor templates — pick the one that matches your chain shape (see docs/chain-decision-tree.md) and delete the other two before drafting, so the directory reflects the chain you’re actually building:

StepDraft fileTemplate
1 (paper-rooted)drafts/01_quote.mdQuote-with-comment
1 (question-rooted, comparative)drafts/01_pico.mdPICO Research Question
1 (question-rooted, descriptive)drafts/01_pcc.mdPCC Research Question
2drafts/02_aida.mdAIDA Sentence
3drafts/03_claim.mdFORRT Claim
4drafts/04_study.mdFORRT Replication Study
5drafts/05_outcome.mdFORRT Replication Outcome
6drafts/06_citation.mdCiTO Citation

Once the chain shape is decided, delete the two step-1 alternatives you aren’t using:

# Paper-rooted chain — keep 01_quote.md:
rm nanopubs/drafts/01_pico.md nanopubs/drafts/01_pcc.md

# Question-rooted, comparative (PICO) — keep 01_pico.md:
rm nanopubs/drafts/01_quote.md nanopubs/drafts/01_pcc.md

# Question-rooted, descriptive (PCC) — keep 01_pcc.md:
rm nanopubs/drafts/01_quote.md nanopubs/drafts/01_pico.md

Keeping all three confuses the audit trail: a reader of the finished repo can’t tell which anchor the chain was actually built from.

Drafting workflow

For each step:

  1. Run the pre-flight checklist in docs/forrt-form-fields.md — before drafting any content.

  2. Open the matching draft file in drafts/.

  3. Write each form field verbatim, in form order. Required fields: provide a value. Optional fields: provide a value, or write *(skip — optional)*.

  4. Have the user review.

  5. The user copy-pastes into the platform UI on https://platform.sciencelive4all.org and publishes.

  6. The user records the resulting URI in PUBLISHED.md.

  7. The next step’s draft references the just-published URI (e.g. the AIDA’s Relates to this nanopublication field is the Quote URI).

Order matters

Each step in the chain references the URI of the previous step:

Don’t try to publish out of order. Don’t forget to update PUBLISHED.md as you go — downstream drafts pull from there.

Optional layers

Once the six-step chain is published, two optional further nanopubs may apply:

After publishing

The published nanopub URI (recorded in PUBLISHED.md) is the canonical, citable record on the nanopub network. The draft file in drafts/ is just the field-by-field local notes used to assemble that submission.

What you do with the drafts after publishing is up to you. The template doesn’t prescribe either way.

Verify the chain before announcing

Once all 6 step URIs are in PUBLISHED.md, run /verify-chain as the final pre-comms check. It fetches each published nanopub, walks the citation graph, and verifies:

A green /verify-chain report is the “safe to LinkedIn-post” signal. A red report names the specific failure so you can retract+supersede the affected step before announcing.

See .claude/skills/verify-chain/SKILL.md for the procedure and docs/programmatic-nanopubs.md for the retract / supersede workflow when fixes are needed.