← Documentation home

Canonical Markdown source · Oct 20, 2018

Managed Linked Art pilot follow-up packet

ops/pilot-follow-up-2026-08-20.md · 81 lines · SHA-256 cc6d524b5f38

Prepared: 2026-08-20

Status: draft for accountable human approval; nothing sent

Why this is the next action

The retained outreach ledger records nine first messages, no replies, and

follow-up dates no later than August 12. Sending another cold batch would widen

the funnel before completing the existing conversations. This packet proposes

one follow-up to each existing recipient through the same authorized channel.

Eligible accounts

  • `museum-of-new-zealand-te-papa-tongarewa`
  • `nasher-museum-of-art-at-duke-university`
  • `smart-museum-of-art`
  • `benton-museum-of-art-at-pomona-college`
  • `center-for-creative-photography`
  • `colby-college-museum-of-art`
  • `allen-memorial-art-museum`
  • `museums-victoria`
  • `art-gallery-of-ontario`

The operator must re-check the original destination and use the same channel.

This repository packet deliberately contains no names, email addresses, phone

numbers, or newly inferred contacts.

Exact follow-up copy

Subject: Follow-up: bounded Linked Art collection pilot

Hello,

I’m following up once on my earlier note about Meta Museum’s Managed Linked Art

Launch Pilot. The offer is a fixed-scope evaluation of one collection export:

reviewed Linked Art records, a small browse/API slice, and an evidence packet

covering source, rights, validation, and unresolved decisions.

If this is relevant to your collection-data plans, would a 20-minute fit call be

useful? I can send the one-page scope first. If it is not relevant, no reply is

needed and I will close the outreach record.

Meta Museum does not claim that your organization needs this work, and this

message does not imply an existing relationship, endorsement, or permission to

use collection data.

Best,

Joseph Chirume

Sun & Rain Works / Meta Museum

https://www.metamuseum.org/pilot

Approval and send boundary

Before any send, an accountable operator must approve:

  1. the exact account IDs and original channels;
  1. the exact copy above, including the sender identity;
  1. one follow-up only, with no automated sequence;
  1. immediate suppression for an opt-out, wrong recipient, or negative reply;
  1. a dated immutable send receipt without personal contact data in this repo.

Approval is not a send. After an approved real send, record each event with:


pnpm pilot:outreach -- --account=<account-id> --stage=followed_up --occurred-at=<ISO timestamp> --owner="<operator>" --evidence=channel=<same-channel> --evidence=messageRef=<provider-receipt> --evidence=closeIfNoReplyAt=<YYYY-MM-DD>

The ledger permits only one follow-up per account and requires a prior sent

event. Do not mislabel a follow-up as `replied` or `qualified`. A reply is not a

qualified conversation until an accountable human applies the qualification

rubric.

Success evidence

pilot or revenue claim.

  • At least one genuine reply tied to a prior sent message.
  • At least one reply qualifies for a bounded buyer conversation.
  • A signed scope and invoice reference remain separately required before a paid