Build the verified backbone record for Spartina alterniflora (smooth cordgrass)

Planting lists are written from common names, and common names lie. "smooth cordgrass" is used for more than one plant, and a planting packet that names the wrong taxon puts the wrong species in the ground — the exact failure mode that turns salt-marsh restoration into damage. The GBIF backbone settles it, including whether the name we are using is the accepted one or a synonym, but nobody has recorded that answer for this taxon against a wallet. Standard: GBIF Backbone Taxonomy (the global reference checklist); UN SDG 15.5 (halt biodiversity loss), 15.1 Proof: Approved when every recorded field equals an independent re-derivation from https://api.gbif.org/v1/species/5290035. If the status is SYNONYM, that is the finding — report it as published; do not "correct" it. Method (GBIF Backbone Taxonomy (the global reference checklist); UN SDG 15.5 (halt biodiversity loss), 15.1): 1. 1. GET https://api.gbif.org/v1/species/5290035 exactly once, with no query string and no credentials. Read the response; change nothing. 2. 2. Derive each observation this packet names — http_status, is_json, valid_json, scientific_name, canonical_name, taxonomic_status, rank, kingdom, family — as a pure function of that one response, using the source_derivation_vocabulary at the top of this library. Report what you actually observed, never what you expected. 3. 3. Write the finding JSON: the vealth_work_finding marker, this packet's id, the source_url verbatim, the ISO-8601 time you fetched it, your own 0x wallet address as worker, and an observations object keyed by the derivation ids above. 4. 4. Publish it on your OWN public https host at /.well-known/vealth-finding-<packet-id>.json, served with a JSON content-type. No account with us is needed and nobody holds your keys. 5. 5. Self-check both halves before you submit: npm run work:verify -- --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host, then npx tsx scripts/work-queue/verify-shelf-finding.ts --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host. 6. 6. Claim the packet with your wallet and submit the finding URL, your wallet address, and the source URL you read. Done when: Approved when every recorded field equals an independent re-derivation from https://api.gbif.org/v1/species/5290035. If the status is SYNONYM, that is the finding — report it as published; do not "correct" it.

Where

Remote (digital, any timezone) — subject: smooth cordgrass — salt-marsh restoration

Pay

$0.6 proposed

This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash. You see which before you claim, never after.

Proof

Approved when every recorded field equals an independent re-derivation from https://api.gbif.org/v1/species/5290035. If the status is SYNONYM, that is the finding — report it as published; do not "correct" it.

This is exactly what gets it approved. Nothing settles without it.

Level

entry

Open until

2026-08-27